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

> Remote attackers can cause a kernel panic and denial of service in Linux SCTP by sending unexpected chunks to a closed session.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 9 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v556-chqj-grw5

## What is CVE-2006-2271?

CVE-2006-2271 is a high-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

The ECNE chunk handling in Linux SCTP (lksctp) before 2.6.17 allows remote attackers to cause a denial of service (kernel panic) via an unexpected chunk when the session is in CLOSED state.

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

It affects 1 product.


Products: Lksctp Lksctp.

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

Upgrade to a fixed version.

## Is CVE-2006-2271 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2271 is a high-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-2271 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-2271/ (Markdown: https://insights.sbomify.com/CVE-2006-2271/index.md)
```

## Sources

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

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