Loading vulnerability…
A race condition in the Linux kernel zswap writeback path permits stale zswap-shrink work to write a previously mapped page to a swap slot after the original zswap entry has been invalidated and that slot has been reused for a different page. The stale local zswap entry can remain referenced while the current entry is replaced in the zswap tree, causing a subsequent swap-in to restore data belonging to the prior page rather than the page currently assigned to that slot. The fix verifies, after swap page-cache allocation in the ZSWAP_SWAPCACHE_NEW case, that the locally held zswap entry is still the entry present in the zswap tree; writeback is aborted if it was replaced or invalidated.
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.
23 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A race condition in Linux kernel memory management's zswap writeback handling.
A Linux kernel memory-management flaw caused by a race condition in zswap writeback.
Linux kernel memory-management flaw involving a zswap writeback race condition.
Linux kernel memory-management zswap writeback race condition.
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.