CVE-2025-38137
BaseFortify
Publication date: 2025-07-03
Last updated on: 2025-11-20
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | 6.11 |
| linux | linux_kernel | 6.11 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel involves a use-after-free issue in the PCI power control (pwrctrl) subsystem. It can be triggered by forcing the rescan_work_func() function to take a long time while simultaneously unloading a pwrctrl driver. The problem arises because outstanding rescan work is not canceled before the driver is unregistered, leading to potential use of freed memory. The fix involves canceling any outstanding rescan work to ensure it completes before the related data structures are cleaned up.
How can this vulnerability impact me? :
This vulnerability can lead to use-after-free conditions, which may cause system instability, crashes, or potentially allow an attacker to execute arbitrary code or escalate privileges if they can manipulate the timing of driver unloading and rescan work execution.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, ensure your Linux kernel is updated to a version that includes the fix for this issue, which cancels outstanding rescan work when unregistering to prevent use-after-free. Avoid unloading pwrctrl drivers while rescan_work_func() is running. Applying the latest kernel patches from your distribution is recommended.