# sctp: clear out_curr if all frag chunks of current msg are pruned

CVE record · `CVE-2022-49838`

- **Identifiers:** `CVE-2022-49838`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 1 May 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 1 May 2025, 14:09 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 to before e27458b18b35caee4b27b37a4a9c503b93cae5cc` (git)
  - affected: `5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 to before 2ea600b598dd3e061854dd4dd5b4c815397dfcea` (git)
  - affected: `5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 to before 3eff34e01062ec08fbb45ce2baaaa644550be821` (git)
  - affected: `5bbbbe32a43199c2b9ea5ea66fab6241c64beb51 to before 2f201ae14ae0f91dbf1cffea7bb1e29e81d4d108` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.15`
  - unaffected: `before 4.15` (semver)
  - unaffected: `5.10.156 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.81 to 5.15.*, inclusive` (semver)
  - unaffected: `6.0.10 to 6.0.*, inclusive` (semver)
  - unaffected: `6.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel SCTP implementation is affected from version 4.15 onward. A flaw where a stream's current message pointer is not cleared after unsent fragments are pruned can cause list corruption and a kernel crash during sending. The source gives few details on what an attacker needs. Upgrade to 5.10.156, 5.15.81, 6.0.10, 6.1 or later.

Written 16 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0022, the 12th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 1 May 2025, 14:09 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-49838)
- 1 May 2025, 15:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-49838)

## Sources

- [CVE List: CVE-2022-49838](https://www.cve.org/CVERecord?id=CVE-2022-49838)
- [NVD: CVE-2022-49838](https://nvd.nist.gov/vuln/detail/CVE-2022-49838)

### References from the CNA

- <https://git.kernel.org/stable/c/e27458b18b35caee4b27b37a4a9c503b93cae5cc>
- <https://git.kernel.org/stable/c/2ea600b598dd3e061854dd4dd5b4c815397dfcea>
- <https://git.kernel.org/stable/c/3eff34e01062ec08fbb45ce2baaaa644550be821>
- <https://git.kernel.org/stable/c/2f201ae14ae0f91dbf1cffea7bb1e29e81d4d108>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2022-49838>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2022-49838/>. Everything for agents: <https://agentprime.io/llms.txt>.
