Affects the Linux kernel (widely deployed); UAF in kernel can cause crashes or privilege escalation across servers and devices.
CVE-2026-74629
Linux kernel net/dibs use-after-free allows kernel crash or privilege escalation.
Is CVE-2026-74629 being exploited?
Not confirmed. CVE-2026-74629 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.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-74629?
CVE-2026-74629 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-74629?
Yes. A fix has been recorded for CVE-2026-74629. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74629 affect?
CVE-2026-74629 affects Linux kernel (net/dibs subsystem), Servers, appliances, and devices running affected kernel versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74629?
Apply vendor kernel patches/upgrade to fixed kernel and reboot affected hosts immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Use-after-free/double-free in net/dibs may allow kernel crash (DoS), local privilege escalation, or kernel-level code execution.
Immediate action required
- affected>= cc21191b584c6f7836b0f10774f8278b7cbfba10 and < ece6426b61241e9bfb41aa131f235168f55229b1
- affected>= cc21191b584c6f7836b0f10774f8278b7cbfba10 and < 7a1df20a8d2cc89e3a442b6e0b43b1cacde8d403
- affected>= cc21191b584c6f7836b0f10774f8278b7cbfba10 and < 9e6869be49064915edb6c8776b27c376cfdb0df5
- affected6.18
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.