# CVE-2006-2274: Denial of service in n/a

> Remote attackers can crash the Linux kernel via crafted SCTP packets causing infinite recursion, requiring kernel patching.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p5qf-q563-3822

## What is CVE-2006-2274?

CVE-2006-2274 is a medium-severity denial of service vulnerability in n/a, published on 9 May 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Linux SCTP (lksctp) before 2.6.17 allows remote attackers to cause a denial of service (infinite recursion and crash) via a packet that contains two or more DATA fragments, which causes an skb pointer to refer back to itself when the full message is reassembled, leading to infinite recursion in the sctp_skb_pull function.

## Which versions are affected by CVE-2006-2274?

It affects 1 product.


Products: Lksctp Stream Control Transmission Protocol.

## How do I fix CVE-2006-2274?

Apply the vendor's patch.

## Is CVE-2006-2274 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-2272](https://insights.sbomify.com/CVE-2006-2272/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-2274 and fix it if it is affected.

What it is: CVE-2006-2274 is a medium-severity denial of service vulnerability in n/a, published on 9 May 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-2274 in the wild and no public exploit code.

Affected product: n/a. 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-2006-2274/ (Markdown: https://insights.sbomify.com/CVE-2006-2274/index.md)
```

## Sources

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

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