Service interruption via dying VPE affinity race
Published Nov 8, 2024 · Updated May 11, 2026
A race condition in Linux kernel GICv4 VPE handling allows local users to interrupt service by changing affinity after unmapping. The VMOVP path accepts an affinity change without checking that vmapp_count marks the VPE as unmapped, while its doorbell remains visible in /proc/irq/. Reachability requires local low-privileged access, GICv4 virtual interrupt support, and winning the narrow unmap-affinity race; the reported consequence is loss of availability.
Summary
What happened
A race condition in Linux kernel GICv4 VPE handling allows local users to interrupt service by changing affinity after unmapping. The VMOVP path accepts an affinity change without checking that vmapp_count marks the VPE as unmapped, while its doorbell remains visible in /proc/irq/. Reachability requires local low-privileged access, GICv4 virtual interrupt support, and winning the narrow unmap-affinity race; the reported consequence is loss of availability.
The record
- CVE
- CVE-2024-50192
- Published
- Nov 8, 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
- Nov 8, 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.6
- Affected versionversion=64edfaa9a2342a3ce34f8cb982c2c2df84db4de3 <01282ab5182f85e42234df2ff42f0ce790f465ff
- Affected versionversion=64edfaa9a2342a3ce34f8cb982c2c2df84db4de3 <1442ee0011983f0c5c4b92380e6853afb513841a
- Affected versionversion=64edfaa9a2342a3ce34f8cb982c2c2df84db4de3 <64b12b061c5488e2d69e67c4eaae5da64fd30bfe
- Affected versionversion=64edfaa9a2342a3ce34f8cb982c2c2df84db4de3 <755b9532c885b8761fb135fedcd705e21e61cccb
- Affected versionversion=64edfaa9a2342a3ce34f8cb982c2c2df84db4de3 <b7d7b7fc876f836f40bf48a87e07ea18756ba196
- Affected versionversion=64edfaa9a2342a3ce34f8cb982c2c2df84db4de3 <d960505a869e66184fff97fb334980a5b797c7c6
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