Loading vulnerability…
CVE-2026-43303 is a Linux kernel memory-management flaw fixed by clearing page->private in free_pages_prepare(). Multiple kernel subsystems, including slub, shmem, and ttm, may use page->private without clearing it before pages are freed. When such pages are later reallocated as higher-order pages and split with split_page(), tail pages can retain stale page->private values from prior use. The swap subsystem assumes newly allocated pages have page->private == 0 and uses that field to track swap count continuations. If a stale nonzero value is present, swap_count_continued() can incorrectly treat the continuation metadata as valid and traverse an uninitialized page->lru list containing poisoned values, resulting in a use-after-free condition and kernel crash during swap-related operations such as swapoff.
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.
7 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.