CVE-2004-2613: Unspecified vulnerability in procfs in the Linux-VServer stable branch for the 2.4 kernel before 1.23 and Linu

This week

HIGH 10.0WATCHLISTDOWNGRADE

CVE-2004-2613 is a high-severity flaw (CVSS 10.0) affecting linux-vserver. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Unspecified vulnerability in procfs in the Linux-VServer stable branch for the 2.4 kernel before 1.23 and Linux-VServer development branch for the 2.4 kernel before 1.3.5 has unspecified impact and attack vectors, related to "write access to specific proc entries from a vserver context", a different vulnerability than CVE-2004-2408.

Why this priority

Critical severity
Public exploit reference
On your watchlist

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	10.0 (High)
EPSS exploit chance	2.5% (top 16%)
CISA exploited list	No
Published	2004-12-31
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: vserver

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2004-12-31 05:00 UTCPublished CVE record published
2026-06-16 22:09 UTCUpdated Record last modified

vserver linux-vserver DOWNGRADE

Affected: 1.3.0 · 1.3.1 · 1.3.2 · 1.3.3 · 1.3.4 · 1.20 · 1.21 · 1.22

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.3.0

1. Check installed version

apt-cache policy linux-vserver || rpm -q linux-vserver || linux-vserver --version

2. No fixed release: DOWNGRADE to a release before 1.3.0 (Debian / Ubuntu)

apt-cache madison linux-vserver sudo apt install linux-vserver=<VERSION_BEFORE_1.3.0> sudo apt-mark hold linux-vserver

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list linux-vserver sudo dnf downgrade linux-vserver-<VERSION_BEFORE_1.3.0> sudo dnf versionlock add linux-vserver

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2004-2613?

linux-vserver: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2004-2613 being exploited?

CVE-2004-2613 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2004-2613 affect?

CVE-2004-2613 affects linux-vserver. Severity is high (CVSS 10.0). Unspecified vulnerability in procfs in the Linux-VServer stable branch for the 2.4 kernel before 1.23 and Linux-VServer development branch for the 2.4 kernel before 1.3.5 has unspecified impact and attack vectors, related to "write access t

How urgent is CVE-2004-2613?

Priority 66/100. Critical severity; Public exploit reference; On your watchlist

Related CVEs

CVE-2006-4243 CRITICAL 9.8 UPGRADE linux vserver 2.6 before 2.6.17 suffers from privilege escalation in remount code.
CVE-2005-0178 MEDIUM 6.2 DOWNGRADE DOWNGRADE Race condition in the setsid function in Linux before 2.6.8.1 allows local users to cause a denial of service
CVE-2004-2408 LOW 3.6 DOWNGRADE Linux VServer 1.27 and earlier, 1.3.9 and earlier, and 1.9.1 and earlier shares /proc permissions across all v
CVE-2003-1288 MEDIUM 5.0 DOWNGRADE Multiple race conditions in Linux-VServer 1.22 with Linux kernel 2.4.23 and SMP allow local users to cause a d

References

← Back to latest CVEs