iio: adc: rzg2l_adc: Set driver data before enabling runtime PM
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
iio: adc: rzg2l_adc: Set driver data before enabling runtime PM
When stress-testing the system by repeatedly unbinding and binding the ADC device in a loop, and the ADC is a supplier for another device (e.g., a thermal hardware block that reads temperature through the ADC), it may happen that the ADC device is runtime-resumed immediately after runtime PM is enabled, triggered by its consumer. At this point, since drvdata is not yet set and the driver's runtime PM callbacks rely on it, a crash can occur. To avoid this, set drvdata just after it was allocated.
From the CVE record · Linux
The Linux kernel's rzg2l_adc driver can crash if its ADC device is runtime-resumed before driver data is set. This can occur during repeated unbinding and binding when another device uses the ADC and triggers the resume. The input does not specify authentication requirements.
Engineers running the Linux kernel with the rzg2l_adc driver should check their installations; affected versions are not specified.