The Linux kernel’s hardware random number generator registration routine fails to remove a device from the global list when a later step of the initialization process fails, leaving the list referencing a freed object. This dangling reference can lead to a use‑after‑free condition if code that called the registration routine frees the object after the error is returned. An attacker who can influence the registration sequence or the object’s lifetime could trigger the use‑after‑free to execute arbitrary code in kernel mode, potentially escalating privileges. The weakness is a classic instance of code not cleaning up state on error, allowing a memory reference to be used after the pointed‑to object has been deallocated.

The flaw resides in the core Linux kernel code common to all distributions. Any system running an affected kernel version without the applied fix is vulnerable. No specific kernel versions are listed in the data, so all unpatched kernels could be impacted.

The EPSS score is reported as less than 1 % and the vulnerability is not listed in the CISA KEV catalog, indicating a very low probability of public exploitation. A use‑after‑free in kernel space typically yields a high severity if successfully exploited, requiring local or elevated privileges. Without a local kernel exploit or a way to inject code through an external interface, the practical risk remains low.