CVE-2025-39774
BaseFortify
Publication date: 2025-09-11
Last updated on: 2025-11-25
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.17 |
| linux | linux_kernel | 6.17 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's rzg2l_adc driver. When the ADC device is repeatedly unbound and bound in a loop during stress testing, and the ADC supplies data to another device (like a thermal sensor), the ADC may be resumed by runtime power management before its driver data (drvdata) is set. Since the runtime PM callbacks depend on drvdata being set, this can cause a system crash. The fix involves setting the driver data immediately after allocation to prevent this issue.
How can this vulnerability impact me? :
This vulnerability can cause system crashes during runtime power management operations involving the ADC device, especially under stress conditions where the device is repeatedly unbound and bound. Such crashes can lead to system instability, potential data loss, or disruption of services relying on the ADC and its consumer devices.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version where the issue is resolved by setting the driver data (drvdata) before enabling runtime PM for the rzg2l_adc driver. Avoid stress-testing scenarios that repeatedly unbind and bind the ADC device until the fix is applied.