CVE-2026-74586
Linux kernel SCTP use-after-free in ASCONF handling enabling kernel memory corruption.
Is CVE-2026-74586 being exploited?
Not confirmed. CVE-2026-74586 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.50% probability of exploitation in the next 30 days.
How severe is CVE-2026-74586?
CVE-2026-74586 is rated Critical. 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-74586?
Yes. A fix has been recorded for CVE-2026-74586. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74586 affect?
CVE-2026-74586 affects Linux kernel (SCTP subsystem), Kernels with SCTP enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74586?
Apply vendor kernel updates; disable SCTP until patched if immediate patching is not possible.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
An authenticated remote SCTP peer can trigger a use-after-free, causing kernel memory corruption leading to crashes, privilege escalation, or potential RCE.
Immediate action required
- affected>= 6af29ccc223b0feb6fc6112281c3fa3cdb1afddf and < c0f973bb5118dd1b146cda3fcc8af6f6057befec
- affected>= 6af29ccc223b0feb6fc6112281c3fa3cdb1afddf and < 3b539b317cd052236fed0350364ff1268996ba46
- affected>= 6af29ccc223b0feb6fc6112281c3fa3cdb1afddf and < db9d8e3b670f841755bc2018f178472dc6064d27
- affected>= 6af29ccc223b0feb6fc6112281c3fa3cdb1afddf and < 31efa656cf6aface26e88f038c14f22ee6ca1500
- affected>= 6af29ccc223b0feb6fc6112281c3fa3cdb1afddf and < 291accf36febce751021888de5f15090f4875b56
- affected>= 6af29ccc223b0feb6fc6112281c3fa3cdb1afddf and < ca33df36aa0143a1d04f57d2086020c12e7eddb7
- affected>= 6af29ccc223b0feb6fc6112281c3fa3cdb1afddf and < 163847552a571bd55094291f4ffcdc1de0f14a7b
- affected>= 6af29ccc223b0feb6fc6112281c3fa3cdb1afddf and < beb33f8ee1ca83acddb2a5ae80f3d22ec550b4c3
- affected3.2
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.