Loading vulnerability…
CVE-2024-50192 is a race condition in the Linux kernel irqchip/gic-v4 virtual interrupt-controller implementation. During virtual processing element (VPE) teardown, userspace can request a VPE affinity change after the VPE has been unmapped but while its associated doorbell interrupt remains visible through the IRQ interface. This can cause a VMOVP operation to be issued against a dying, unmapped VPE. The fix checks vmapp_count, which records whether the VPE remains mapped, and rejects the operation when the VPE is no longer mapped. The mapping-state tracking was made common to the GICv4.0 and GICv4.1 implementations.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel GIC-v4 interrupt-controller flaw involving a VMOVP operation on a dying virtual processing element.
Linux kernel GIC-v4 interrupt-controller flaw allowing VMOVP on a dying virtual processing element.
Linux kernel GICv4 interrupt-controller flaw involving VMOVP operations against a virtual processing element that is being destroyed.
A Linux kernel GICv4 interrupt-controller flaw involving VMOVP operations on a dying virtual processing element.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.