Wi-Fi failure via stale resume interrupt race
Published Nov 9, 2024 · Updated May 11, 2026
A race condition in affected Linux builds from 2.6.25 through 6.11.6 allows local users to interrupt iwl4965 Wi-Fi service after resume. The il_pci_resume function enables interrupts without first clearing a stale device interrupt, racing resume against restart work queued by the interrupt handler. Exposure requires iwl4965 hardware and hibernation; the race can leave the wireless hardware unavailable and trigger a kernel warning.
Summary
What happened
A race condition in affected Linux builds from 2.6.25 through 6.11.6 allows local users to interrupt iwl4965 Wi-Fi service after resume. The il_pci_resume function enables interrupts without first clearing a stale device interrupt, racing resume against restart work queued by the interrupt handler. Exposure requires iwl4965 hardware and hibernation; the race can leave the wireless hardware unavailable and trigger a kernel warning.
The record
- CVE
- CVE-2024-50234
- Published
- Nov 9, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-367, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 9, 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.25
- Affected versionversion=e655b9f03f41c7a84fb74d6619abf844d7f2ab65 <07c90acb071b9954e1fecb1e4f4f13d12c544b34
- Affected versionversion=e655b9f03f41c7a84fb74d6619abf844d7f2ab65 <23f9cef17ee315777dbe88d5c11ff6166e4d0699
- Affected versionversion=e655b9f03f41c7a84fb74d6619abf844d7f2ab65 <271d282ecc15d7012e71ca82c89a6c0e13a063dd
- Affected versionversion=e655b9f03f41c7a84fb74d6619abf844d7f2ab65 <8ac22fe1e2b104c37e4fecd97735f64bd6349ebc
- Affected versionversion=e655b9f03f41c7a84fb74d6619abf844d7f2ab65 <8af8294d369a871cdbcdbb4d13b87d2d6e490a1f
- Affected versionversion=e655b9f03f41c7a84fb74d6619abf844d7f2ab65 <9d89941e51259c2b0b8e9c10c6f1f74200d7444f
- Affected versionversion=e655b9f03f41c7a84fb74d6619abf844d7f2ab65 <cedf0f1db8d5f3524339c2c6e35a8505b0f1ab73
- Affected versionversion=e655b9f03f41c7a84fb74d6619abf844d7f2ab65 <d0231f43df473e2f80372d0ca150eb3619932ef9
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