CVE-2026-43336 Details
Description
In the Linux kernel, the following vulnerability has been resolved: lib/crypto: chacha: Zeroize permuted_state before it leaves scope Since the ChaCha permutation is invertible, the local variable 'permuted_state' is sufficient to compute the original 'state', and thus the key, even after the permutation has been done. While the kernel is quite inconsistent about zeroizing secrets on the stack (and some prominent userspace crypto libraries don't bother at all since it's not guaranteed to work anyway), the kernel does try to do it as a best practice, especially in cases involving the RNG. Thus, explicitly zeroize 'permuted_state' before it goes out of scope.
A vulnerability exists in the Linux kernel's handling of the ChaCha20 permutation within the crypto library. The issue arises because the permutation is invertible, allowing the local variable 'permuted_state' to be used to reconstruct the original 'state' and key, even after the permutation. This vulnerability is present in the Linux kernel stable tree. The problem stems from the kernel's inconsistent practice of zeroing out sensitive data on the stack, a flaw that some widely used user-space crypto libraries also share. However, the kernel attempts to follow best practices, particularly regarding the random number generator (RNG). To mitigate this vulnerability, 'permuted_state' should be explicitly zeroed before it goes out of scope.
The vulnerability has been addressed in the Linux kernel. Users should upgrade to the latest version that includes this fix.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/066c760acead1fb743bae294dbd89f479ae43b9b | kernel.org | Patch |
| https://git.kernel.org/stable/c/1933249263c3a98df79992f61a566476e4163bcc | kernel.org | Patch |
| https://git.kernel.org/stable/c/1d761e5a7340c46479fb2399598f331e4fe2c633 | kernel.org | Patch |
| https://git.kernel.org/stable/c/91999af43ca2125e3b2c18fcfc02912ada02efc3 | kernel.org | Patch |
| https://git.kernel.org/stable/c/b416a4245f04a450c67a13e6d96056c37c5b33fe | kernel.org | Patch |
| https://git.kernel.org/stable/c/bd62d9b44464a6c20a34a74068e7a784d0afa04a | kernel.org | Patch |
| https://git.kernel.org/stable/c/e5046823f8fa3677341b541a25af2fcb99a5b1e0 | kernel.org | Patch |
| https://git.kernel.org/stable/c/e90ee961af515a484f091678ce58a4c3f7b73b02 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.2, < 5.10.253 >= 5.11, < 5.15.203 >= 5.16, < 6.1.169 >= 6.2, < 6.6.135 >= 6.7, < 6.12.82 >= 6.13, < 6.18.22 >= 6.19, < 6.19.12 7.0 rc1 7.0 rc2 7.0 rc3 7.0 rc4 7.0 rc5 7.0 rc6 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| May 15, 2026 | Initial Analysis | [email protected] |
| May 11, 2026 | CVE Modified | kernel.org |
| May 8, 2026 | New CVE Received | kernel.org |