https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 22:30:04 +0000 https://vulnerability.circl.lu/vuln/cve-2025-39804 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>lib/crypto: arm64/poly1305: Fix register corruption in no-SIMD contexts</p> <p>Restore the SIMD usability check that was removed by commit a59e5468a921 (&#34;crypto: arm64/poly1305 - Add block-only interface&#34;).</p> <p>This safety check is cheap and is well worth eliminating a footgun. While the Poly1305 functions should not be called when SIMD registers are unusable, if they are anyway, they should just do the right thing instead of corrupting random tasks&#39; registers and/or computing incorrect MACs. Fixing this is also needed for poly1305_kunit to pass.</p> <p>Just use may_use_simd() instead of the original crypto_simd_usable(), since poly1305_kunit won&#39;t rely on crypto_simd_disabled_for_test.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>lib/crypto: arm64/poly1305: Fix register corruption in no-SIMD contexts</p> <p>Restore the SIMD usability check that was removed by commit a59e5468a921 (&#34;crypto: arm64/poly1305 - Add block-only interface&#34;).</p> <p>This safety check is cheap and is well worth eliminating a footgun. While the Poly1305 functions should not be called when SIMD registers are unusable, if they are anyway, they should just do the right thing instead of corrupting random tasks&#39; registers and/or computing incorrect MACs. Fixing this is also needed for poly1305_kunit to pass.</p> <p>Just use may_use_simd() instead of the original crypto_simd_usable(), since poly1305_kunit won&#39;t rely on crypto_simd_disabled_for_test.</p> https://vulnerability.circl.lu/vuln/cve-2025-39804