The flaw originates from a race condition in the DMB loopback code where a node can be freed after its reference count is decremented but before the lookup lock is released. This permits a concurrent thread to access a freed object, resulting in a use‑after‑free situation. The vulnerability is a classic Use‑after‑free weakness and could allow an attacker to corrupt kernel memory, potentially leading to code execution or privilege escalation on a system with local access.

All Linux kernel installations that include the DMB loopback handling code before the commit cc21191b584c were potentially affected. The CPE information lists only the generic Linux kernel, and version data is not supplied; it is inferred that any kernel version containing the code in the described state is vulnerable.

The EPSS score is < 1% and the vulnerability is not listed in the CISA KEV catalog, indicating no known public exploits at this time. However, for systems running older kernel code, the risk is significant because the flaw resides in the kernel and requires a local attacker with the ability to trigger concurrent attach, detach, or unregister operations. The explicit mention of a use‑after‑free and the required race conditions suggest that exploitation would be local and privileged, with the potential for arbitrary code execution in kernel mode if successfully triggered.