crypto: atmel-sha204a - fix heap info leak on I2C transfer failure
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f4d347fb1309b69ea6f817a17e6b2893c8d754b7, Kernel 0d6db386133d9230befb77967bbf130443964860, Kernel 28cc179252347718f97045dd5ea74165609dbd7d and 12 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <f4d347fb1309b69ea6f817a17e6b2893c8d754b7, >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <0d6db386133d9230befb77967bbf130443964860, >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <28cc179252347718f97045dd5ea74165609dbd7d, >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <4e76d85e505b7451925efbcd67c015e8c2440c68, >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <72bbf11ba14bd7d5fbf31a1ec42fff608b657f74, >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <94abda77b57a35b82bba0365bad072d94d67ffe9, >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <a430b5b6d2ddd2b266330f8507a655be1148347d, >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <bcac9052e19490231ff6e0678a06bd2fcf8db3af, =5.3 | f4d347fb1309b69ea6f817a17e6b2893c8d754b7, 0d6db386133d9230befb77967bbf130443964860, 28cc179252347718f97045dd5ea74165609dbd7d, 4e76d85e505b7451925efbcd67c015e8c2440c68, 72bbf11ba14bd7d5fbf31a1ec42fff608b657f74, 94abda77b57a35b82bba0365bad072d94d67ffe9, a430b5b6d2ddd2b266330f8507a655be1148347d, bcac9052e19490231ff6e0678a06bd2fcf8db3af |
| linux-kernel: Kernel | >=5.16.0 <6.1.188, >=5.3.0 <5.10.270, >=6.13.0 <6.18.52, >=6.19.0 <7.2.6, >=6.2.0 <6.6.157, >=6.7.0 <6.12.110, >=5.11.0 <5.15.221 | 6.1.188, 5.10.270, 6.18.52, 7.2.6, 6.6.157, 6.12.110, 5.15.221 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket