Linux kernel vulnerability causing kernel memory corruption across widely deployed systems; high impact (DoS/privilege escalation) and affects core infrastructure.
CVE-2026-74469
Linux SCTP transport_count wrap leads to kernel OOB write, causing crash or escalation.
Is CVE-2026-74469 being exploited?
Not confirmed. CVE-2026-74469 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.47% probability of exploitation in the next 30 days.
How severe is CVE-2026-74469?
CVE-2026-74469 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-74469?
Yes. A fix has been recorded for CVE-2026-74469. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74469 affect?
CVE-2026-74469 affects Linux kernel (SCTP subsystem). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74469?
Install vendor kernel security updates and reboot affected hosts.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Out-of-bounds kernel write via SCTP transport_count wrap; can cause kernel crash (DoS) or enable privilege escalation.
Immediate action required
- affected>= 8f840e47f190cbe61a96945c13e9551048d42cef and < b453e00da1211e997b82743d28af7714c59c05c8
- affected>= 8f840e47f190cbe61a96945c13e9551048d42cef and < dfea32dd76f390e3155177b0038cc47b01386198
- affected>= 8f840e47f190cbe61a96945c13e9551048d42cef and < 80f48523a0fe42db2e7375dff4e38a25c117090a
- affected>= 8f840e47f190cbe61a96945c13e9551048d42cef and < 546221b86ceeba0d8fec92d46a0604bb7b62be07
- affected>= 8f840e47f190cbe61a96945c13e9551048d42cef and < 09e722030e8148ba4ed1e42c6b2ea57bda9f9895
- affected>= 8f840e47f190cbe61a96945c13e9551048d42cef and < 4ba5bf7ed50f235ea4581de8e7a0002f4ed287b0
- affected>= 8f840e47f190cbe61a96945c13e9551048d42cef and < 6201cd1d70f1670c5b31ac506e7ab2fa7b8e7f75
- affected>= 8f840e47f190cbe61a96945c13e9551048d42cef and < bd0e9289e2642f6a5c54faad304ce0f41e926d22
- affected4.7
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.