Vulnerability Description
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.
References
- https://git.kernel.org/stable/c/2926031acba100d0c18fcfaa7a2ed29609318848
- https://git.kernel.org/stable/c/c27e360545373b7aee9862a5beef3b9fb3df0c25
- https://git.kernel.org/stable/c/fe79571f40434b257d68cbfb7b3ae93a794d8a11
FAQ
What is CVE-2026-74617?
CVE-2026-74617 is a documented vulnerability. 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 in...
How severe is CVE-2026-74617?
CVSS scoring is not yet available for CVE-2026-74617. Check NVD for updates.
Is there a patch for CVE-2026-74617?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.