CVE-2025-39804
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2025-39804
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2025-39804.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2025-39804
- Downstream
- Published
- 2025-09-15T12:36:46.483Z
- Modified
- 2025-12-02T18:56:48.544866Z
- Summary
- lib/crypto: arm64/poly1305: Fix register corruption in no-SIMD contexts
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
lib/crypto: arm64/poly1305: Fix register corruption in no-SIMD contexts
Restore the SIMD usability check that was removed by commit a59e5468a921 ("crypto: arm64/poly1305 - Add block-only interface").
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' registers and/or computing incorrect MACs. Fixing this is also needed for poly1305_kunit to pass.
Just use mayusesimd() instead of the original cryptosimdusable(), since poly1305kunit won't rely on cryptosimddisabledfor_test.
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/39xxx/CVE-2025-39804.json" }- References
-
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- https://git.kernel.org/stable/c/eec76ea5a7213c48529a46eed1b343e5cee3aaab
- https://git.kernel.org/stable/c/ef74efa598b7bbc5c24509f7f56af2806f81c339
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/39xxx/CVE-2025-39804.json
- https://nvd.nist.gov/vuln/detail/CVE-2025-39804