The Linux kernel’s Qualcomm hardware random number generator driver exposed two independent interfaces, crypto_rng and hwrng, that accessed the same hardware registers simultaneously. The implementation failed to synchronize these concurrent accesses, allowing calls to both interfaces at the same time. This race condition can repeat random output or produce values that are not truly random, undermining any cryptographic processes that rely on that randomness.

Linux kernels where the qcom-rng driver is present. The flaw applies to all distributions using the upstream kernel that have not yet removed the crypto_rng interface for this driver.

No CVSS score or EPSS score is listed, and the vulnerability is not in the CISA KEV catalog. Based on the description, the likely attack vector is an adversary who can invoke both RNG interfaces, intentionally or unintentionally, to induce the vulnerable concurrent access. Because the issue stems from internal register contention rather than an external input, exploitation requires internal code execution or a scenario where both interfaces are invoked from privileged or untrusted code paths. The risk is thus moderate, contingent on the presence of dual RNG usage in the system.