CVE-2026-80871: crypto: xilinx-trng - Remove crypto_rng interface
In the Linux kernel, the following vulnerability has been resolved:
crypto: xilinx-trng - Remove cryptorng interface
Implementing the cryptorng interface has no purpose, as it isn't used in practice. It's being removed from other drivers too. Just remove it. This leaves hwrng, which is actually used.
Tagging with 'Cc stable' due to the bugs that this removes:
- xtrngtrnggenerate() sometimes returned success even when it didn't fill in all the bytes.
- It was possible for xtrngtrnggenerate() and xtrnghwrngtrngread() to run concurrently and interfere with each other, as the locking code in xtrnghwrngtrngread() was broken.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Remove
Remove
crypto: xilinx-trng - Remove crypto_rng interfacefrom your environment.Remove the crypto_rng interface from the xilinx-trng driver (it is not used).
Event History
Frequently Asked Questions
Which systems are exposed to the reported issues?
Systems using the Linux kernel Xilinx TRNG driver are affected where its crypto_rng interface is present. The remaining hwrng interface is described as the interface that is actually used.
What failures could occur before the fix?
The crypto_rng generation function could report success without filling all requested bytes. It could also run concurrently with the hardware RNG read function, with the two operations interfering because the read-side locking was broken.
What is the remediation?
Update to a kernel containing the change that removes the Xilinx TRNG crypto_rng interface. The change is tagged for stable kernels because it removes the underlying bugs.