CVE-2026-93159

crypto: atmel-sha204a - fix heap info leak on I2C transfer failure

N/A
Published: September 17, 2026 at 04:11 PM UTC
Updated: October 19, 2026 at 10:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.3da001fb651b00e1deeaf24767dd691ae8152a4f5
Vendor states this is fixed in 0d6db386133d9230befb77967bbf130443964860 (fixed)
Vendor states this is fixed in 28cc179252347718f97045dd5ea74165609dbd7d (fixed)
Vendor states this is fixed in 4e76d85e505b7451925efbcd67c015e8c2440c68 (fixed)
Vendor states this is fixed in 72bbf11ba14bd7d5fbf31a1ec42fff608b657f74 (fixed)
Vendor states this is fixed in 94abda77b57a35b82bba0365bad072d94d67ffe9 (fixed)
Vendor states this is fixed in a430b5b6d2ddd2b266330f8507a655be1148347d (fixed)
Vendor states this is fixed in bcac9052e19490231ff6e0678a06bd2fcf8db3af (fixed)
Vendor states this is fixed in f4d347fb1309b69ea6f817a17e6b2893c8d754b7 (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 5.3 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card