# CVE-2004-1144: Unknown vulnerability in the 32bit emulation code in Linux 2.4 on AMD64 systems allows local users to gain privileges.


- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 31 Dec 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-rc3j-q64p-mx9g

## What is CVE-2004-1144?

CVE-2004-1144 is a high-severity vulnerability in Linux kernel, published on 31 Dec 2004. 

### Official description

Unknown vulnerability in the 32bit emulation code in Linux 2.4 on AMD64 systems allows local users to gain privileges.

## Which versions are affected by CVE-2004-1144?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2004-1144?

Upgrade to a fixed version.

## Is CVE-2004-1144 being exploited?

There is no known exploitation of CVE-2004-1144 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1144 and fix it if it is affected.

What it is: CVE-2004-1144 is a high-severity vulnerability in Linux kernel, published on 31 Dec 2004. 
Exploitation: There is no known exploitation of CVE-2004-1144 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2004-1144/ (Markdown: https://insights.sbomify.com/CVE-2004-1144/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2004-1144
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2004-1144
- OSV: https://osv.dev/vulnerability/CVE-2004-1144

---
From sbomify Insights: https://insights.sbomify.com/CVE-2004-1144/
Summaries are generated and may contain mistakes; the official description above is the record.