lib/crypto: chacha: Zeroize permuted_state before it leaves scope
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.42% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 066c760acead1fb743bae294dbd89f479ae43b9b, 1933249263c3a98df79992f61a566476e4163bcc, 1d761e5a7340c46479fb2399598f331e4fe2c633.
Low priority for now. Upgrade to Linux Linux 066c760acead1fb743bae294dbd89f479ae43b9b, 1933249263c3a98df79992f61a566476e4163bcc, 1d761e5a7340c46479fb2399598f331e4fe2c633 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 8, 2026
- Updated
- Aug 5, 2026
- EPSS
- 0.4% · 35th percentile
- CWE
- —
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.2 and later · before 5.10.253
- linux linux kernel5.11 and later · before 5.15.203
- linux linux kernel5.16 and later · before 6.1.169
- linux linux kernel6.2 and later · before 6.6.135
- linux linux kernel6.7 and later · before 6.12.82
- linux linux kernel6.13 and later · before 6.18.22
- linux linux kernel6.19 and later · before 6.19.12
- linux linux kernel7.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.2affected
- c08d0e647305c3f8f640010a56c9e4bafb9488d3 and later · before e90ee961af515a484f091678ce58a4c3f7b73b02affected · git
- c08d0e647305c3f8f640010a56c9e4bafb9488d3 and later · before b416a4245f04a450c67a13e6d96056c37c5b33feaffected · git
- c08d0e647305c3f8f640010a56c9e4bafb9488d3 and later · before bd62d9b44464a6c20a34a74068e7a784d0afa04aaffected · git
- c08d0e647305c3f8f640010a56c9e4bafb9488d3 and later · before 066c760acead1fb743bae294dbd89f479ae43b9baffected · git
- c08d0e647305c3f8f640010a56c9e4bafb9488d3 and later · before 1d761e5a7340c46479fb2399598f331e4fe2c633affected · git
- c08d0e647305c3f8f640010a56c9e4bafb9488d3 and later · before 1933249263c3a98df79992f61a566476e4163bccaffected · git
- c08d0e647305c3f8f640010a56c9e4bafb9488d3 and later · before 91999af43ca2125e3b2c18fcfc02912ada02efc3affected · git
- c08d0e647305c3f8f640010a56c9e4bafb9488d3 and later · before e5046823f8fa3677341b541a25af2fcb99a5b1e0affected · git
- before 4.2not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.170-1 | 6.1.170-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.12-1 | 6.19.12-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2026-43333May 8, 2026 · bpf: reject direct access to nullable PTR_TO_BUF pointers22Monitor
- ← EarlierCVE-2026-43335May 8, 2026 · interconnect: qcom: sm8450: Fix NULL pointer dereference in icc_link_nodes()22Monitor
- Later →CVE-2026-43340May 8, 2026 · comedi: Reinit dev->spinlock between attachments to low-level drivers22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 066c760acead1fb743bae294dbd89f479ae43b9b | Vendor (CNA) |
| Linux Linux | 1933249263c3a98df79992f61a566476e4163bcc | Vendor (CNA) |
| Linux Linux | 1d761e5a7340c46479fb2399598f331e4fe2c633 | Vendor (CNA) |
| Linux Linux | 91999af43ca2125e3b2c18fcfc02912ada02efc3 | Vendor (CNA) |
| Linux Linux | b416a4245f04a450c67a13e6d96056c37c5b33fe | Vendor (CNA) |
| Linux Linux | bd62d9b44464a6c20a34a74068e7a784d0afa04a | Vendor (CNA) |
| Linux Linux | e5046823f8fa3677341b541a25af2fcb99a5b1e0 | Vendor (CNA) |
| Linux Linux | e90ee961af515a484f091678ce58a4c3f7b73b02 | Vendor (CNA) |
| debian:linux | 6.1.170-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/1933249263c3a98df79992f61a566476e4163bcc
- git.kernel.org/stable/c/1d761e5a7340c46479fb2399598f331e4fe2c633
- git.kernel.org/stable/c/91999af43ca2125e3b2c18fcfc02912ada02efc3
- git.kernel.org/stable/c/b416a4245f04a450c67a13e6d96056c37c5b33fe
- git.kernel.org/stable/c/bd62d9b44464a6c20a34a74068e7a784d0afa04a
- git.kernel.org/stable/c/e5046823f8fa3677341b541a25af2fcb99a5b1e0
- git.kernel.org/stable/c/e90ee961af515a484f091678ce58a4c3f7b73b02
Vendor advisories and official records. Exploit/PoC links are deliberately left out.