Answer in brief
CVE-2026-43336 records a Unknown severity vulnerability in lib/crypto: chacha: Zeroize permuted_state before it leaves scope. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-43336 records a Unknown severity vulnerability in lib/crypto: chacha: Zeroize permuted_state before it leaves scope. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c08d0e647305c3f8f640010a56c9e4bafb9488d3 <e90ee961af515a484f091678ce58a4c3f7b73b02 || >=c08d0e647305c3f8f640010a56c9e4bafb9488d3 <b416a4245f04a450c67a13e6d96056c37c5b33fe || >=c08d0e647305c3f8f640010a56c9e4bafb9488d3 <bd62d9b44464a6c20a34a74068e7a784d0afa04a || >=c08d0e647305c3f8f640010a56c9e4bafb9488d3 <066c760acead1fb743bae294dbd89f479ae43b9b || >=c08d0e647305c3f8f640010a56c9e4bafb9488d3 <1d761e5a7340c46479fb2399598f331e4fe2c633 || >=c08d0e647305c3f8f640010a56c9e4bafb9488d3 <1933249263c3a98df79992f61a566476e4163bcc || >=c08d0e647305c3f8f640010a56c9e4bafb9488d3 <91999af43ca2125e3b2c18fcfc02912ada02efc3 || >=c08d0e647305c3f8f640010a56c9e4bafb9488d3 <e5046823f8fa3677341b541a25af2fcb99a5b1e0 | e90ee961af515a484f091678ce58a4c3f7b73b02, b416a4245f04a450c67a13e6d96056c37c5b33fe, bd62d9b44464a6c20a34a74068e7a784d0afa04a, 066c760acead1fb743bae294dbd89f479ae43b9b, 1d761e5a7340c46479fb2399598f331e4fe2c633, 1933249263c3a98df79992f61a566476e4163bcc, 91999af43ca2125e3b2c18fcfc02912ada02efc3, e5046823f8fa3677341b541a25af2fcb99a5b1e0 |
| Linux/Linuxgeneric | 4.2 | Not reported |
Published upstream
May 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c08d0e647305c3f8f640010a56c9e4bafb9488d3 <e90ee961af515a484f091678ce58a4c3f7b73b02 || >=c08d0e647305c3f8f640010a56c9e4bafb9488d3 <b416a4245f04a450c67a13e6d96056c37c5b33fe || >=c08d0e647305c3f8f640010a56c9e4bafb9488d3 <bd62d9b44464a6c20a34a74068e7a784d0afa04a || >=c08d0e647305c3f8f640010a56c9e4bafb9488d3 <066c760acead1fb743bae294dbd89f479ae43b9b || >=c08d0e647305c3f8f640010a56c9e4bafb9488d3 <1d761e5a7340c46479fb2399598f331e4fe2c633 || >=c08d0e647305c3f8f640010a56c9e4bafb9488d3 <1933249263c3a98df79992f61a566476e4163bcc || >=c08d0e647305c3f8f640010a56c9e4bafb9488d3 <91999af43ca2125e3b2c18fcfc02912ada02efc3 || >=c08d0e647305c3f8f640010a56c9e4bafb9488d3 <e5046823f8fa3677341b541a25af2fcb99a5b1e0 | e90ee961af515a484f091678ce58a4c3f7b73b02, b416a4245f04a450c67a13e6d96056c37c5b33fe, bd62d9b44464a6c20a34a74068e7a784d0afa04a, 066c760acead1fb743bae294dbd89f479ae43b9b, 1d761e5a7340c46479fb2399598f331e4fe2c633, 1933249263c3a98df79992f61a566476e4163bcc, 91999af43ca2125e3b2c18fcfc02912ada02efc3, e5046823f8fa3677341b541a25af2fcb99a5b1e0 |
| Linux/Linuxgeneric | 4.2 | Not reported |
Published upstream
May 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.