CVE-2026-93159

Unknown

Last modified

CVE-2026-93159 is a vulnerability of currently unknown severity. 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.

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= da001fb651b00e1deeaf24767dd691ae8152a4f5, < a430b5b6d2ddd2b266330f8507a655be1148347d; >= da001fb651b00e1deeaf24767dd691ae8152a4f5, < 4e76d85e505b7451925efbcd67c015e8c2440c68; >= da001fb651b00e1deeaf24767dd691ae8152a4f5, < bcac9052e19490231ff6e0678a06bd2fcf8db3af; >= da001fb651b00e1deeaf24767dd691ae8152a4f5, < 28cc179252347718f97045dd5ea74165609dbd7d; >= da001fb651b00e1deeaf24767dd691ae8152a4f5, < 0d6db386133d9230befb77967bbf130443964860; >= da001fb651b00e1deeaf24767dd691ae8152a4f5, < f4d347fb1309b69ea6f817a17e6b2893c8d754b7; >= da001fb651b00e1deeaf24767dd691ae8152a4f5, < 94abda77b57a35b82bba0365bad072d94d67ffe9; >= da001fb651b00e1deeaf24767dd691ae8152a4f5, < 72bbf11ba14bd7d5fbf31a1ec42fff608b657f74
LinuxLinux5.3

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-93159?
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.
How severe is CVE-2026-93159?
Severity scoring for CVE-2026-93159 is pending analysis.
How do I fix CVE-2026-93159?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-93159?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST