CVE-2024-35939 affects the Linux kernel dma-direct subsystem. In TDX environments, an untrusted host can cause the memory-encryption transition performed by dma_set_decrypted() to fail while leaving the affected memory shared/decrypted. The DMA error path could then free those shared pages back to the page allocator. The fix retains (leaks) the pages when dma_set_decrypted() fails, preventing decrypted/shared memory from being returned to general allocation.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel DMA-direct flaw that can leak pages when dma_set_decrypted() fails.
Linux kernel DMA-direct page leak on dma_set_decrypted failure.
Linux kernel DMA-direct page leak on dma_set_decrypted failure.
Linux kernel DMA-direct page leak upon dma_set_decrypted failure.
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.