Resource exhaustion via missed interrupt allocation teardown
Published Sep 17, 2026 · Updated Sep 17, 2026
Resource leakage in Linux irqchip/gic-v3-its allows local users to exhaust kernel resources via failed interrupt allocation. The its_vpe_irq_domain_alloc() error path frees earlier interrupts but skips its_vpe_teardown() for the failing interrupt, retaining its resources. Exposure requires the VPE allocation path and an allocation failure; denial of service is reported, but a specific crash or hang is not documented.
Summary
What happened
Resource leakage in Linux irqchip/gic-v3-its allows local users to exhaust kernel resources via failed interrupt allocation. The its_vpe_irq_domain_alloc() error path frees earlier interrupts but skips its_vpe_teardown() for the failing interrupt, retaining its resources. Exposure requires the VPE allocation path and an allocation failure; denial of service is reported, but a specific crash or hang is not documented.
The record
- CVE
- CVE-2026-92524
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-772, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 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.14
- Affected versionversion=7d75bbb4bc1ad90386776459d37e4ddfe605671e <05c199d6b806ed1cc64807062f9986f11315e8ab
- Affected versionversion=7d75bbb4bc1ad90386776459d37e4ddfe605671e <0d1951a1935a11c197272dbd38349033f0ef8991
- Affected versionversion=7d75bbb4bc1ad90386776459d37e4ddfe605671e <325ff3e78c64cd619d52b99f7c8b09a3f31e1495
- Affected versionversion=7d75bbb4bc1ad90386776459d37e4ddfe605671e <6cd7e9b5463e1bceddcaf4acec6ca0f12553455b
- Affected versionversion=7d75bbb4bc1ad90386776459d37e4ddfe605671e <6eb1f1414bf70185dad2525ecac5411db551faa2
- Affected versionversion=7d75bbb4bc1ad90386776459d37e4ddfe605671e <82bccf7f9a12bf0eec9774968f6a853020ea26d3
- Affected versionversion=7d75bbb4bc1ad90386776459d37e4ddfe605671e <c4643bcb3bdda96b7292d6ab6ed196755a5bc304
- Affected versionversion=7d75bbb4bc1ad90386776459d37e4ddfe605671e <d324c4353f64190a032c78d6e07be6d57ddfb2f1
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started