lib/crypto: arm64/poly1305: Fix register corruption in no-SIMD contexts
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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 may_use_simd() instead of the original crypto_simd_usable(), since poly1305_kunit won't rely on crypto_simd_disabled_for_test.
From the CVE record · Linux
The Linux kernel’s arm64 Poly1305 code lacked a check for whether SIMD registers could be used. If its functions are called when SIMD is unavailable, they can corrupt other tasks’ registers or compute incorrect MACs. The input does not specify an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with arm64 Poly1305 should check whether their kernels include the fix; affected versions are not specified.