CVE-2026-93159 — crypto: atmel-sha204a - fix heap info leak on I2C transfer failure
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ da001fb651b00e1deeaf24767dd691ae8152a4f5 and < a430b5b6d2ddd2b266330f8507a655be1148347d≥ da001fb651b00e1deeaf24767dd691ae8152a4f5 and < 4e76d85e505b7451925efbcd67c015e8c2440c68≥ da001fb651b00e1deeaf24767dd691ae8152a4f5 and < bcac9052e19490231ff6e0678a06bd2fcf8db3af≥ da001fb651b00e1deeaf24767dd691ae8152a4f5 and < 28cc179252347718f97045dd5ea74165609dbd7d≥ da001fb651b00e1deeaf24767dd691ae8152a4f5 and < 0d6db386133d9230befb77967bbf130443964860≥ da001fb651b00e1deeaf24767dd691ae8152a4f5 and < f4d347fb1309b69ea6f817a17e6b2893c8d754b7≥ da001fb651b00e1deeaf24767dd691ae8152a4f5 and < 94abda77b57a35b82bba0365bad072d94d67ffe9≥ da001fb651b00e1deeaf24767dd691ae8152a4f5 and < 72bbf11ba14bd7d5fbf31a1ec42fff608b657f74 and 1 moreversion 5.3 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/94abda77b57a35b82bba0365bad072d94d67ffe9
- git.kernel.org/stable/c/bcac9052e19490231ff6e0678a06bd2fcf8db3af
- git.kernel.org/stable/c/f4d347fb1309b69ea6f817a17e6b2893c8d754b7
- git.kernel.org/stable/c/4e76d85e505b7451925efbcd67c015e8c2440c68
- git.kernel.org/stable/c/0d6db386133d9230befb77967bbf130443964860
- git.kernel.org/stable/c/72bbf11ba14bd7d5fbf31a1ec42fff608b657f74
- git.kernel.org/stable/c/a430b5b6d2ddd2b266330f8507a655be1148347d
- git.kernel.org/stable/c/28cc179252347718f97045dd5ea74165609dbd7d
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 17h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 17h
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-93159 is "crypto: atmel-sha204a - fix heap info leak on I2C transfer failure", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.