crypto: atmel-sha204a - fix heap info leak on I2C transfer failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ da001fb651b00e1deeaf24767dd691ae8152a4f5 · < f4d347fb1309b69ea6f817a17e6b2893c8d754b7| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The atmel-sha204a RNG path can leave stale state after an I2C transfer fails. Subsequent reads may interpret that state as valid RNG data, potentially leaking heap information. The input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels with the atmel-sha204a driver should check their installations; affected versions are not specified.