CVE Tools

CVE-2026-74469

sctp: prevent peer transport count overflow

No known exploitation. EPSS puts it in the 50th percentile. No fix published yet.

Published Updated Sources: CVE.org, NVD

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

Steps

Written by AI from the record
  1. Check whether your linux kernel has SCTP enabled or loaded, and whether untrusted users can obtain local accounts or run workloads on the system.
  2. Install your operating system vendor’s kernel update containing one of these fixes: b453e00da1211e997b82743d28af7714c59c05c8, dfea32dd76f390e3155177b0038cc47b01386198, 80f48523a0fe42db2e7375dff4e38a25c117090a, 546221b86ceeba0d8fec92d46a0604bb7b62be07, 09e722030e8148ba4ed1e42c6b2ea57bda9f9895, 4ba5bf7ed50f235ea4581de8e7a0002f4ed287b0, 6201cd1d70f1670c5b31ac506e7ab2fa7b8e7f75, or bd0e9289e2642f6a5c54faad304ce0f41e926d22.
  3. Restart into the updated kernel and confirm the running kernel is the updated vendor release.
  4. If an update must wait, remove unneeded SCTP support and restrict untrusted local accounts and workloads.

What it is

From the CVE record

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.

In plain language

Written by AI from the record

CVE-2026-74469 is a serious flaw in the linux kernel that a low-privileged local user could use to take over or crash a server, so businesses with shared or untrusted user access should install their vendor’s kernel update promptly.

Local privilege escalation and denial of service in SCTP: peer transport_count can overflow, causing SCTP sock_diag to under-allocate its peer payload and write out of bounds.

If you're affected

  • Full server takeover
  • Server crashes
  • Sensitive data exposure
  • Business-service disruption

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS50th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.7% chance of exploitation activity in the next 30 days, which ranks it in the 50th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

5 events over 12 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Record updated
  3. Record updated
  4. Publishedrecord updated

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Scored 8.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Linux, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store