Kernel memory corruption via PCI rescan race
Published Jul 3, 2025 · Updated May 11, 2026
Use-after-free in Linux kernel PCI power control from 6.11 before 6.15.3 allows local users to corrupt kernel memory during driver removal. The unregister path cleans up pwrctrl data structures while delayed rescan_work_func work can still reference them. Triggering the race requires extending that work and using CAP_SYS_ADMIN or CAP_SYS_MODULE to unbind or unload the pwrctrl driver.
Summary
What happened
Use-after-free in Linux kernel PCI power control from 6.11 before 6.15.3 allows local users to corrupt kernel memory during driver removal. The unregister path cleans up pwrctrl data structures while delayed rescan_work_func work can still reference them. Triggering the race requires extending that work and using CAP_SYS_ADMIN or CAP_SYS_MODULE to unbind or unload the pwrctrl driver.
The record
- CVE
- CVE-2025-38137
- Published
- Jul 3, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jul 3, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.11
- Affected versionversion=8f62819aaace77dd85037ae766eb767f8c4417ce <8b926f237743f020518162c62b93cb7107a2b5eb
- Affected versionversion=8f62819aaace77dd85037ae766eb767f8c4417ce <b3ad6d23fec23fbef382ce9ea640c37446593cf5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo