CVE-2025-21861 is a resource-lifecycle flaw in the Linux kernel's device-memory migration finalization logic. After successful migration, folio_migrate_flags() and mem_cgroup_migrate() transfer memory-cgroup metadata to the destination folio and clear the source folio's memcg_data. After failed migration, the destination folio's memcg_data remains unset. migrate_device_finalize() can incorrectly call folio_putback_lru() on these folios pending release, adding them to the least-recently-used list without valid memory-cgroup metadata. This triggers memory-cgroup warnings, as reproduced by Heterogeneous Memory Management self-tests.
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.
36 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel device-memory migration flaw incorrectly places folios awaiting release onto the least-recently-used list, triggering memory-cgroup warnings. The advisory rates it Medium, with a CVSS v3 score of 5.5 and an availability impact requiring local access and low privileges. The description notes that releasing the final folio reference likely removes it again without further problems.
Linux kernel device-memory migration folio LRU handling flaw.
A Linux kernel memory-management flaw in device-page migration finalization. Under successful or failed migration paths, a folio with unset memory-control-group data could be unnecessarily placed on the LRU list, causing memory-control-group warnings and potentially affecting availability.
Linux kernel device-memory migration folio handling flaw.
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.