CVE-2026-74617
In the Linux kernel, the following vulnerability has been resolved: dibs: initialise dibs->lock in dibs_dev_alloc() dibs->lock is initialised by dibs_dev_add(), but a dibs device can already take interrupts before that call: ism_probe() runs ism_dev_init(), and hence request_irq(), before it calls dibs_dev_add(). No client can have registered a dmb at that point, so no dmb interrupt can occur, but a GID event interrupt can, and ism_handle_irq() takes dibs->lock unconditionally on entry, before it inspects anything else. Initialise the lock in dibs_dev_alloc() instead, so that it is valid as soon as a driver can publish the device to its interrupt handler.
Affected versions
Linux kernel versions
6.18
and later are affected. Fixed in
6.18.45,
7.1.9,
7.2
and their respective stable series.
References
3 totalFrequently asked questions
-
What is CVE-2026-74617?
CVE-2026-74617 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 6.18 onward and has been patched in 6.18.45, 7.1.9 and 7.2. CVE-2026-74617 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-74617?
Yes. CVE-2026-74617 has been patched. Fixed versions include 6.18.45, 7.1.9 and 7.2. If you are running Linux kernel 6.18 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-74617 actively exploited?
No. CVE-2026-74617 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.