https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 20:27:46 +0000 https://vulnerability.circl.lu/vuln/cve-2026-80871 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>crypto: xilinx-trng - Remove crypto_rng interface</p> <p>Implementing the crypto_rng interface has no purpose, as it isn&#39;t used in practice. It&#39;s being removed from other drivers too. Just remove it. This leaves hwrng, which is actually used.</p> <p>Tagging with &#39;Cc stable&#39; due to the bugs that this removes:</p> <p>- xtrng_trng_generate() sometimes returned success even when it didn&#39;t fill in all the bytes.</p> <p>- It was possible for xtrng_trng_generate() and xtrng_hwrng_trng_read() to run concurrently and interfere with each other, as the locking code in xtrng_hwrng_trng_read() was broken.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>crypto: xilinx-trng - Remove crypto_rng interface</p> <p>Implementing the crypto_rng interface has no purpose, as it isn&#39;t used in practice. It&#39;s being removed from other drivers too. Just remove it. This leaves hwrng, which is actually used.</p> <p>Tagging with &#39;Cc stable&#39; due to the bugs that this removes:</p> <p>- xtrng_trng_generate() sometimes returned success even when it didn&#39;t fill in all the bytes.</p> <p>- It was possible for xtrng_trng_generate() and xtrng_hwrng_trng_read() to run concurrently and interfere with each other, as the locking code in xtrng_hwrng_trng_read() was broken.</p> https://vulnerability.circl.lu/vuln/cve-2026-80871