Kernel crash via late shared IRQ teardown
Published Jul 30, 2024 · Updated May 11, 2026
Denial of service in the Linux lima DRM driver allows local users to crash the kernel by removing the driver during shared IRQ teardown. Device-managed shared IRQ handlers remain registered after the removal callbacks disable device clocks, so an interrupt handler can access registers while their clocks are off. Triggering the crash requires lima driver removal on a kernel built with CONFIG_DEBUG_SHIRQ; no data disclosure or modification is reported.
Summary
What happened
Denial of service in the Linux lima DRM driver allows local users to crash the kernel by removing the driver during shared IRQ teardown. Device-managed shared IRQ handlers remain registered after the removal callbacks disable device clocks, so an interrupt handler can access registers while their clocks are off. Triggering the crash requires lima driver removal on a kernel built with CONFIG_DEBUG_SHIRQ; no data disclosure or modification is reported.
The record
- CVE
- CVE-2024-42127
- Published
- Jul 30, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 30, 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=5.2
- Affected versionversion=a1d2a6339961efc078208dc3b2f006e9e9a8e119 <04d531b9a1875846d4f89953b469ad463aa7a770
- Affected versionversion=a1d2a6339961efc078208dc3b2f006e9e9a8e119 <0a487e977cb8897ae4c51ecd34bbaa2b005266c9
- Affected versionversion=a1d2a6339961efc078208dc3b2f006e9e9a8e119 <0d60c43df59ef01c08dc7b0c45495178f9d05a13
- Affected versionversion=a1d2a6339961efc078208dc3b2f006e9e9a8e119 <17fe8b75aaf0bb1bdc31368963446b421c22d0af
- Affected versionversion=a1d2a6339961efc078208dc3b2f006e9e9a8e119 <25d0d9b83d855cbc5d5aa5ae3cd79d55ea0c84a8
- Affected versionversion=a1d2a6339961efc078208dc3b2f006e9e9a8e119 <a6683c690bbfd1f371510cb051e8fa49507f3f5e
- Affected versionversion=a1d2a6339961efc078208dc3b2f006e9e9a8e119 <b5daf9217a50636a969bc1965f827878aeb09ffe
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