CVE-2026-93159: crypto: atmel-sha204a - fix heap info leak on I2C transfer failure
Noroxi assessment
Priority: Monitor (action score 0/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.22% (FIRST EPSS).
- Fixed version: Linux Linux 0d6db386133d9230befb77967bbf130443964860, 28cc179252347718f97045dd5ea74165609dbd7d, 4e76d85e505b7451925efbcd67c015e8c2440c68.
Low priority for now. Upgrade to Linux Linux 0d6db386133d9230befb77967bbf130443964860, 28cc179252347718f97045dd5ea74165609dbd7d, 4e76d85e505b7451925efbcd67c015e8c2440c68 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: crypto: atmel-sha204a - fix heap info leak on I2C transfer failure The nonblocking RNG path allocates a work_data structure to track the state of an in-flight asynchronous I2C request. This pointer is stored in rng->priv and later consumed by the read path once the transaction completes. If the underlying I2C transfer fails, the completion callback is invoked with a non-zero status. In this case, the allocated work_data is not usable for producing RNG output and must not remain associated with the hwrng state. Previously, the failure path only logged a warning but left the pointer state uncleared, which can result in subsequent read attempts observing stale state and interpreting it as valid completion data. Fix this by freeing the pending work_data. The I2C transaction reports an error. This ensures that failed requests do not leave residual state behind that could be interpreted as valid RNG data on later reads. Clearing rng->priv is done at the subsequent call to nonblocking read.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
—
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
- 5.3affected
- da001fb651b00e1deeaf24767dd691ae8152a4f5 and later · before a430b5b6d2ddd2b266330f8507a655be1148347daffected · git
- da001fb651b00e1deeaf24767dd691ae8152a4f5 and later · before 4e76d85e505b7451925efbcd67c015e8c2440c68affected · git
- da001fb651b00e1deeaf24767dd691ae8152a4f5 and later · before bcac9052e19490231ff6e0678a06bd2fcf8db3afaffected · git
- da001fb651b00e1deeaf24767dd691ae8152a4f5 and later · before 28cc179252347718f97045dd5ea74165609dbd7daffected · git
- da001fb651b00e1deeaf24767dd691ae8152a4f5 and later · before 0d6db386133d9230befb77967bbf130443964860affected · git
- da001fb651b00e1deeaf24767dd691ae8152a4f5 and later · before f4d347fb1309b69ea6f817a17e6b2893c8d754b7affected · git
- da001fb651b00e1deeaf24767dd691ae8152a4f5 and later · before 94abda77b57a35b82bba0365bad072d94d67ffe9affected · git
- da001fb651b00e1deeaf24767dd691ae8152a4f5 and later · before 72bbf11ba14bd7d5fbf31a1ec42fff608b657f74affected · git
- before 5.3not 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.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-93157Sep 17, 2026 · hwrng: xilinx-trng - propagate timeout before any data is read0Monitor
- ← EarlierCVE-2026-93158Sep 17, 2026 · crypto: sa2ul - stop probe if context pool creation fails0Monitor
- Later →CVE-2026-93160Sep 17, 2026 · crypto: atmel-ecc - reject hardware ECDH without a public key0Monitor
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 | 0d6db386133d9230befb77967bbf130443964860 | Vendor (CNA) |
| Linux Linux | 28cc179252347718f97045dd5ea74165609dbd7d | Vendor (CNA) |
| Linux Linux | 4e76d85e505b7451925efbcd67c015e8c2440c68 | Vendor (CNA) |
| Linux Linux | 72bbf11ba14bd7d5fbf31a1ec42fff608b657f74 | Vendor (CNA) |
| Linux Linux | 94abda77b57a35b82bba0365bad072d94d67ffe9 | Vendor (CNA) |
| Linux Linux | a430b5b6d2ddd2b266330f8507a655be1148347d | Vendor (CNA) |
| Linux Linux | bcac9052e19490231ff6e0678a06bd2fcf8db3af | Vendor (CNA) |
| Linux Linux | f4d347fb1309b69ea6f817a17e6b2893c8d754b7 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · 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
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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/28cc179252347718f97045dd5ea74165609dbd7d
- git.kernel.org/stable/c/4e76d85e505b7451925efbcd67c015e8c2440c68
- git.kernel.org/stable/c/72bbf11ba14bd7d5fbf31a1ec42fff608b657f74
- git.kernel.org/stable/c/94abda77b57a35b82bba0365bad072d94d67ffe9
- git.kernel.org/stable/c/a430b5b6d2ddd2b266330f8507a655be1148347d
- git.kernel.org/stable/c/bcac9052e19490231ff6e0678a06bd2fcf8db3af
- git.kernel.org/stable/c/f4d347fb1309b69ea6f817a17e6b2893c8d754b7
Vendor advisories and official records. Exploit/PoC links are deliberately left out.