Kernel-level bug in Linux (dibs/ism IRQ path) affects core infrastructure used broadly; can cause system-wide disruption and potential privilege escalation.
CVE-2026-74617
Linux kernel dibs/ism IRQ uninitialized lock may cause kernel crash and escalation.
Is CVE-2026-74617 being exploited?
Not confirmed. CVE-2026-74617 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.44% probability of exploitation in the next 30 days.
How severe is CVE-2026-74617?
CVE-2026-74617 is rated Critical with a CVSS score of 9.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-74617?
Yes. A fix has been recorded for CVE-2026-74617. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74617 affect?
CVE-2026-74617 affects Linux kernel (dibs/ism driver). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74617?
Install vendor kernel security update and reboot affected systems immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Uninitialized lock in IRQ handler can trigger kernel crashes (DoS) and may enable local privilege escalation via kernel memory corruption.
Immediate action required
- affected>= cc21191b584c6f7836b0f10774f8278b7cbfba10 and < fe79571f40434b257d68cbfb7b3ae93a794d8a11
- affected>= cc21191b584c6f7836b0f10774f8278b7cbfba10 and < 2926031acba100d0c18fcfaa7a2ed29609318848
- affected>= cc21191b584c6f7836b0f10774f8278b7cbfba10 and < c27e360545373b7aee9862a5beef3b9fb3df0c25
- 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.