# CVE-2026-74469: sctp: prevent peer transport count overflow

> An integer overflow in the Linux kernel SCTP implementation allows remote attackers to cause memory corruption and potential code execution via crafted peer transport counts.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** AZL-96329, BELL-CVE-2026-74469, DEBIAN-CVE-2026-74469, GHSA-772m-42gr-vc4c, UBUNTU-CVE-2026-74469

## What is CVE-2026-74469?

CVE-2026-74469 is a high-severity vulnerability in Linux, published on 15 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

sctp: prevent peer transport count overflow

sctp_assoc_add_peer() increments the association's 16-bit transport_count
for every new unique peer. Adding the 65,536th transport wraps the count to
zero.

SCTP sock_diag uses transport_count to reserve the INET_DIAG_PEERS payload,
then copies one sockaddr_storage for every entry in transport_addr_list.
After the wrap, a diagnostic dump reserves an empty payload and writes
8 MiB of peer addresses past the skb tail.

Reject a new unique peer when transport_count has reached U16_MAX. Perform
the check after the existing-peer lookup so a duplicate address continues
to return its existing transport at the limit.

## Which versions are affected by CVE-2026-74469?


## How do I fix CVE-2026-74469?

Apply the vendor's patch.

## Is CVE-2026-74469 being exploited?

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

Public exploit code:

- Tracking DiagSpill (CVE-2026-74469), the Linux kernel SCTP sock_diag heap overflow (github_poc): https://github.com/suominen/diagspill
- CVE-2026-74469 (github_poc): https://github.com/0xredash/CVE-2026-74469
- CVE-2026-74469 DiagSpill (github_poc): https://github.com/HORKimhab/CVE-2026-74469

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74469 and fix it if it is affected.

What it is: CVE-2026-74469 is a high-severity vulnerability in Linux, published on 15 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74469 in the wild and no public exploit code.

Affected product: Linux. 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-2026-74469/ (Markdown: https://insights.sbomify.com/CVE-2026-74469/index.md)
```

## Sources

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

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