CVE-2026-43336
lib/crypto: chacha: Zeroize permuted_state before it leaves scope
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.2
References 8
git.kernel.org
- stable/c/e90ee961af515a484f091678ce58a4c3f7b73b02
- stable/c/b416a4245f04a450c67a13e6d96056c37c5b33fe
- stable/c/bd62d9b44464a6c20a34a74068e7a784d0afa04a
- stable/c/066c760acead1fb743bae294dbd89f479ae43b9b
- stable/c/1d761e5a7340c46479fb2399598f331e4fe2c633
- stable/c/1933249263c3a98df79992f61a566476e4163bcc
- stable/c/91999af43ca2125e3b2c18fcfc02912ada02efc3
- stable/c/e5046823f8fa3677341b541a25af2fcb99a5b1e0