Bug 2394620 (CVE-2025-39774) - CVE-2025-39774 kernel: iio: adc: rzg2l_adc: Set driver data before enabling runtime PM
Summary: CVE-2025-39774 kernel: iio: adc: rzg2l_adc: Set driver data before enabling r...
Keywords:
Status: NEW
Alias: CVE-2025-39774
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-09-11 17:02 UTC by OSIDB Bzimport
Modified: 2025-11-26 08:22 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-09-11 17:02:49 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.