Kernel crash via unlocked PCI device pointer
Published Jul 29, 2024 · Updated Aug 5, 2026
Race condition in affected Linux kernel releases from 3.7 allows local users to crash PowerPC systems during PCI device removal. eeh_pe_report_edev() reads edev->pdev->bus without holding the PCI rescan/remove lock, so concurrent removal can change the pointer before it is copied. Reachability requires local access to a PowerPC system using PCI Enhanced Error Handling and a device-removal race; the reported consequence is a kernel crash.
Summary
What happened
Race condition in affected Linux kernel releases from 3.7 allows local users to crash PowerPC systems during PCI device removal. eeh_pe_report_edev() reads edev->pdev->bus without holding the PCI rescan/remove lock, so concurrent removal can change the pointer before it is copied. Reachability requires local access to a PowerPC system using PCI Enhanced Error Handling and a device-removal race; the reported consequence is a kernel crash.
The record
- CVE
- CVE-2024-41064
- Published
- Jul 29, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 29, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=3.7
- Affected versionversion=9b3c76f08122f5efdbe4992a64b8478cc92dd983 <033c51dfdbb6b79ab43fb3587276fa82d0a329e1
- Affected versionversion=9b3c76f08122f5efdbe4992a64b8478cc92dd983 <428d940a8b6b3350b282c14d3f63350bde65c48b
- Affected versionversion=9b3c76f08122f5efdbe4992a64b8478cc92dd983 <4bc246d2d60d071314842fa448faa4ed39082aff
- Affected versionversion=9b3c76f08122f5efdbe4992a64b8478cc92dd983 <4fad7fef847b6028475dd7b4c14fcb82b3e51274
- Affected versionversion=9b3c76f08122f5efdbe4992a64b8478cc92dd983 <8836e1bf5838ac6c08760e0a2dd7cf6410aa7ff3
- Affected versionversion=9b3c76f08122f5efdbe4992a64b8478cc92dd983 <a1216e62d039bf63a539bbe718536ec789a853dd
- Affected versionversion=9b3c76f08122f5efdbe4992a64b8478cc92dd983 <f23c3d1ca9c4b2d626242a4e7e1ec1770447f7b5
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