Loading vulnerability…
CVE-2024-26810 is a race condition in the Linux kernel VFIO PCI subsystem's handling of external legacy INTx interrupt masking. Configuration-space writes affecting the PCI DisINTx state could execute concurrently with INTx configuration changes performed through VFIO ioctls. The affected path tested INTx configuration state without holding the interrupt gate lock, despite the interrupt type being updated under that lock. The fix introduces locking wrappers for external INTx masking operations, serializing these configuration paths with core interrupt configuration handling.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Locking flaw in Linux kernel VFIO PCI external interrupt masking operations.
Linux kernel VFIO PCI interrupt-masking synchronization flaw.
Linux kernel VFIO PCI external INTx masking synchronization flaw.
Linux kernel VFIO PCI interrupt-handling locking flaw affecting external INTx masking operations.
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.