Improper memory management in the dibs driver causes a use‑after‑free or double‑free when a dibs device is removed or a device addition fails. A continuing interrupt handler may reference the freed dmb_clientid_arr array, corrupting kernel memory and potentially leading to system instability or privilege escalation. The weakness is a classic Use‑After‑Free flaw.

All Linux kernel builds that include the dibs driver before the patch are potentially affected. The vendor is Linux, and the attack surface covers every kernel release that has not yet incorporated the fix; no specific version range is provided, so any kernel with the old implementation is at risk.

No EPSS score or KEV listing indicates that this vulnerability has not yet been widely observed in the wild, but the lack of a CVSS score does not diminish the potential severity. A kernel UAF of this nature can be highly consequential, yet an attacker would need the ability to trigger the related driver operations—typically requiring privileged or local system access—and must time the exploit while a pending interrupt remains active. The overall risk level for environments running the affected kernel and exposing the dibs subsystem is high.