Service interruption via unreclaimed CPU interrupt vectors
Published Jun 21, 2024 · Updated May 11, 2026
Resource exhaustion in the Linux kernel allows local users to interrupt service by leaking x86 CPU interrupt vectors during CPU offlining. When affinity migration is deferred, irq_needs_fixup() can bypass irq_force_complete_move(), and later cleanup clears prev_vector without reclaiming it from vector_matrix. The race requires the old CPU to go offline before the interrupt fires on its new CPU, and repeated leaks can exhaust available vectors.
Summary
What happened
Resource exhaustion in the Linux kernel allows local users to interrupt service by leaking x86 CPU interrupt vectors during CPU offlining. When affinity migration is deferred, irq_needs_fixup() can bypass irq_force_complete_move(), and later cleanup clears prev_vector without reclaiming it from vector_matrix. The race requires the old CPU to go offline before the interrupt fires on its new CPU, and repeated leaks can exhaust available vectors.
The record
- CVE
- CVE-2024-31076
- Published
- Jun 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 21, 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=4.13
- Affected versionversion=f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b <59f86a2908380d09cdc726461c0fbb8d8579c99f
- Affected versionversion=f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b <6752dfcfff3ac3e16625ebd3f0ad9630900e7e76
- Affected versionversion=f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b <9eeda3e0071a329af1eba15f4e57dc39576bb420
- Affected versionversion=f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b <a40209d355afe4ed6d533507838c9e5cd70a76d8
- Affected versionversion=f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b <a6c11c0a5235fb144a65e0cb2ffd360ddc1f6c32
- Affected versionversion=f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b <e9c96d01d520498b169ce734a8ad1142bef86a30
- Affected versionversion=f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b <ebfb16fc057a016abb46a9720a54abf0d4f6abe1
- Affected versionversion=f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b <f5f4675960609d8c5ee95f027fbf6ce380f98372
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