Loading vulnerability…
A use-after-free vulnerability in the Linux kernel's KVM arm64 vGIC-ITS implementation affects translation-cache invalidation in vgic_its_invalidate_cache(). The function iterates the per-ITS translation cache with xa_for_each() and drops a cached IRQ reference with vgic_put_irq(), but in the vulnerable logic it releases the iterated pointer rather than only the entry actually removed by xa_erase(). Because xa_erase() is atomic and multiple invalidation paths can run concurrently without mutual exclusion, two or more contexts can observe the same cache entry, erase it, and each drop the same cache-held reference. This results in a double put that can free a vgic IRQ object while it is still mapped by an interrupt translation entry. The flaw is therefore a race-triggered use-after-free in KVM/arm64's virtual Interrupt Translation Service code and has been publicly associated with guest-to-host escape research under the name ITScape.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (3 hidden).
Repository contains a real C-based proof-of-concept exploit for CVE-2026-46316, a guest-to-host escape in Linux KVM/arm64 caused by a race in vGIC-ITS cache invalidation. Structure is small and focused: README.md explains the vulnerability, affected versions, and usage; assets/write-up.md provides deep technical root-cause and exploit-chain analysis; build.sh compiles the PoC against an unmodified Linux kernel selftests tree; qemu.sh launches an arm64 QEMU TCG environment with GICv3/ITS enabled for safe testing; poc.c is the main exploit. The exploit is not a scanner or detector. It creates a KVM guest via /dev/kvm, populates and races the ITS translation cache from guest-side actions, triggers a double-put/use-after-free in in-kernel KVM, and pivots that into host kernel code execution. The PoC is tuned for a specific target build (Linux v7.1-rc6 with bundled config) and uses hardcoded addresses/offsets, so it is operational but not broadly weaponized. Its demonstrated payload is simple: execute a host-side command path (/bin/touch) from kernel context to create /ITScape as a root-owned marker file. Attack surface is primarily hypervisor/local: an attacker controlling a guest on a vulnerable arm64 KVM host, with guest root privileges, can exploit the host through emulated GIC/ITS MMIO without relying on QEMU userspace emulation. The repository emphasizes that the bug is in in-kernel KVM, independent of QEMU, though QEMU TCG is used here only as a safe lab harness. Notable fingerprintable artifacts include /dev/kvm, /bin/touch, /ITScape, the Linux selftests build path, and the referenced vulnerable/fixed kernel commits.
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.
63 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A separate KVM guest escape vulnerability affecting Arm64 systems, mentioned as related prior research.
A separate earlier KVM/arm64 escape vulnerability mentioned only as background comparison.
A Linux kernel KVM arm64 vgic-its vulnerability fixed as part of this OpenShift Container Platform 4.19.40 security update.
A kernel KVM arm64 vgic-its vulnerability related to incorrect handling of translation cache references.
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.