Loading vulnerability…
CVE-2025-21861 is an improper memory-management state handling flaw in the Linux kernel mm/migrate_device subsystem. In migrate_device_finalize(), the kernel could call folio_putback_lru() for a folio that was being released after device-memory migration. Following successful migration, memory-cgroup migration clears the source folio's memcg_data; after failed migration, the destination folio's memcg_data is unset. Re-adding either folio to the LRU despite this state triggers a memory-cgroup validation warning. The corrected flow avoids placing folios pending release back on the LRU.
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.
32 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel device-memory migration folio handling flaw.
A Linux kernel memory-management flaw in device-memory migration finalization. Under successful or failed migration paths, a folio without valid memory-cgroup data could be unnecessarily returned to the LRU while being freed, causing memory-cgroup warnings.
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.