Kernel-level use-after-free in widely deployed Linux BPF sockmap can lead to privilege escalation or kernel code execution across many servers.
CVE-2026-74589
Use-after-free in Linux BPF sockmap allowing kernel memory corruption.
Is CVE-2026-74589 being exploited?
Not confirmed. CVE-2026-74589 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.14% probability of exploitation in the next 30 days.
How severe is CVE-2026-74589?
CVE-2026-74589 is rated High with a CVSS score of 8.4. 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-74589?
Yes. A fix has been recorded for CVE-2026-74589. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74589 affect?
CVE-2026-74589 affects Linux kernel (BPF, sockmap / tcp_bpf_sendmsg). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74589?
Apply vendor kernel updates and reboot affected hosts immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Use-after-free in BPF sockmap (tcp_bpf_sendmsg) causing kernel memory corruption; may enable local privilege escalation or kernel-level code execution.
Patch when possible
- affected>= 604326b41a6fb9b4a78b6179335decee0365cd8c and < 41b7da0cb72ca5aa1e62b68dab323d0791fc6bdf
- affected>= 604326b41a6fb9b4a78b6179335decee0365cd8c and < 9b4fbc371a6ecf1b4e43b5a629015cc0830d8de3
- affected>= 604326b41a6fb9b4a78b6179335decee0365cd8c and < 90a19b0894ba79a699b48cf44421b36fbd566e99
- affected>= 604326b41a6fb9b4a78b6179335decee0365cd8c and < d192cff2a37d59206dabe6ec2e60ceac6271f274
- affected>= 604326b41a6fb9b4a78b6179335decee0365cd8c and < 4c9d9aa809c261dc0490a0e19d675f7e8e4c85bf
- affected>= 604326b41a6fb9b4a78b6179335decee0365cd8c and < a14e4ef1d90c3418f01b3b6b8fd3a40a0a208a10
- affected>= 604326b41a6fb9b4a78b6179335decee0365cd8c and < 1cec526cf0a2227395f2c2f4b671cb052ff0b00e
- affected>= 604326b41a6fb9b4a78b6179335decee0365cd8c and < a76624733730e541e4955fdecf506af2f6b20558
- affected4.20
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.