dbcve.org
Linux KernelOperating system · Linux

CVE-2004-1070

HIGH · 7.2 CVSS v2.0 Published 2005-01-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The load_elf_binary function in the binfmt_elf loader (binfmt_elf.c) in Linux kernel 2.4.x up to 2.4.27, and 2.6.x up to 2.6.8, does not properly check return values from calls to the kernel_read function, which may allow local users to modify sensitive memory in a setuid program and execute arbitrary code.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The load_elf_binary function in the Linux kernel's binfmt_elf.c ELF binary loader fails to properly check return values from kernel_read() calls when loading ELF binaries. This improper error handling can lead to memory corruption when loading setuid programs, potentially allowing local attackers to execute arbitrary code with elevated privileges.

MitigationApply the upstream kernel patch that adds proper return value checking for kernel_read() calls in load_elf_binary, or upgrade the kernel to a version beyond 2.4.27/2.6.8 where this issue is resolved.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:= 2.4.0= 2.4.1= 2.4.2= 2.4.3= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9= 2.4.10= 2.4.11
Enterprise LinuxOperating system
Affected:= 2.1= 3.0
Enterprise Linux DesktopOperating system
Affected:= 3.0
Fedora CoreOperating system
Affected:= core_2.0= core_3.0
Linux Advanced WorkstationOperating system
Affected:= 2.1
Suse LinuxOperating system
Affected:= 1.0= 8= 8.1= 8.2= 9.0= 9.1= 9.2
Secure LinuxOperating system
Affected:= 1.5= 2.0= 2.1= 2.2
Turbolinux ServerOperating system
Affected:= 10.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the running kernel version
    Run 'uname -r' to get the exact kernel version string
    Affected if The version matches 2.4.0 through 2.4.11, or the major.minor is 2.4.x with patch level 11 or lower
  2. Confirm the kernel series is 2.4.x
    Check that the kernel is from the 2.4 branch. This vulnerability only affects 2.4.x kernels, not 2.6.x or later
    Affected if The kernel version string begins with '2.4.'
  3. Verify ELF binary format support is present
    Check that the system uses ELF executables: run 'file /bin/ls' - if it shows 'ELF' the system loads ELF binaries and binfmt_elf is active
    Affected if The system executes ELF binaries and the ELF binary loader is in use
  4. Confirm setuid binaries exist on the system
    Run 'ls -la /bin/su' or 'ls -l /usr/bin/passwd' to verify the presence of setuid programs
    Affected if Setuid binaries are present, as the vulnerability triggers when loading setuid ELF programs
  5. Check if running a vendor-supplied affected kernel
    Check /proc/version or 'cat /etc/redhat-release' / 'cat /etc/SuSE-release' to identify if the kernel is from an affected vendor version (RHEL 2.1/3.0, Fedora Core 2/3, SuSE, Trustix, Turbolinux as listed)
    Affected if The kernel comes from an affected vendor distribution version listed in the CVE

The system is affected if it runs a Linux 2.4.x kernel version 2.4.11 or lower (or a vendor kernel derived from these versions), as the vulnerability exists in the load_elf_binary function of binfmt_elf.c when loading setuid ELF programs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the upstream kernel patch that adds proper return value checking for kernel_read() calls in load_elf_binary, or upgrade the kernel to a version beyond 2.4.27/2.6.8 where this issue is resolved.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2004-1070 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2004-1070 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data