# CVE-2004-1137: Memory corruption in n/a

> Local and remote attackers can execute arbitrary code or cause denial of service via IGMP handling flaws in the Linux kernel.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Dec 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-vqwc-f978-m55f

## What is CVE-2004-1137?

CVE-2004-1137 is a critical memory corruption vulnerability in Linux kernel, published on 15 Dec 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple vulnerabilities in the IGMP functionality for Linux kernel 2.4.22 to 2.4.28, and 2.6.x to 2.6.9, allow local and remote attackers to cause a denial of service or execute arbitrary code via (1) the ip_mc_source function, which decrements a counter to -1, or (2) the igmp_marksources function, which does not properly validate IGMP message parameters and performs an out-of-bounds read.

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

It affects 2 products.


Products: Linux kernel, Ubuntu Ubuntu Linux.

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

Apply the vendor's patch.

## Is CVE-2004-1137 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1137 exists.

Public exploit code:

- Linux Kernel 2.4.22-28/2.6.9 - 'igmp.c' Local Denial of Service (exploitdb)

## 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-1137 and fix it if it is affected.

What it is: CVE-2004-1137 is a critical memory corruption vulnerability in Linux kernel, published on 15 Dec 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1137 exists.

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-1137/ (Markdown: https://insights.sbomify.com/CVE-2004-1137/index.md)
```

## Sources

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

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