Kernel crash via runtime-idle driver-removal race
Published May 17, 2024 · Updated May 11, 2026
Race condition in affected Linux kernel branches allows local users to crash the kernel during PCI driver removal through runtime PM callbacks. In pci_device_remove(), pm_runtime_get_sync() can return while rtsx_pci_runtime_idle() is still executing, so driver teardown races the active callback and causes an unhandled page fault. Exploitation requires local low-privileged access and the callback to be running during driver removal; the bounded consequence is a kernel crash.
Summary
What happened
Race condition in affected Linux kernel branches allows local users to crash the kernel during PCI driver removal through runtime PM callbacks. In pci_device_remove(), pm_runtime_get_sync() can return while rtsx_pci_runtime_idle() is still executing, so driver teardown races the active callback and causes an unhandled page fault. Exploitation requires local low-privileged access and the callback to be running during driver removal; the bounded consequence is a kernel crash.
The record
- CVE
- CVE-2024-35809
- Published
- May 17, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-362, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 17, 2024CVE 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=2.6.36
- Affected versionversion=f3ec4f87d607f40497afdb5ac03f11e2ea253d52 <47d8aafcfe313511a98f165a54d0adceb34e54b1
- Affected versionversion=f3ec4f87d607f40497afdb5ac03f11e2ea253d52 <6347348c6aba52dda0b33296684cbb627bdc6970
- Affected versionversion=f3ec4f87d607f40497afdb5ac03f11e2ea253d52 <7cc94dd36e48879e76ae7a8daea4ff322b7d9674
- Affected versionversion=f3ec4f87d607f40497afdb5ac03f11e2ea253d52 <900b81caf00c89417172afe0e7e49ac4eb110f4b
- Affected versionversion=f3ec4f87d607f40497afdb5ac03f11e2ea253d52 <9a87375bb586515c0af63d5dcdcd58ec4acf20a6
- Affected versionversion=f3ec4f87d607f40497afdb5ac03f11e2ea253d52 <9d5286d4e7f68beab450deddbb6a32edd5ecf4bf
- Affected versionversion=f3ec4f87d607f40497afdb5ac03f11e2ea253d52 <bbe068b24409ef740657215605284fc7cdddd491
- Affected versionversion=f3ec4f87d607f40497afdb5ac03f11e2ea253d52 <d534198311c345e4b062c4b88bb609efb8bd91d5
- Affected versionversion=f3ec4f87d607f40497afdb5ac03f11e2ea253d52 <d86ad8c3e152349454b82f37007ff6ba45f26989
What conditions does exploitation require?
What is affected?
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