CVE-2022-3623 is a race condition in the Linux kernel memory-management code, specifically follow_page_pte() in mm/gup.c. Racing access can result in a poisoned page-table entry (PTE), causing an erroneous kernel state and a denial-of-service condition. The issue was fixed upstream in Linux kernel 6.1-rc1.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel page-table handling denial-of-service vulnerability.
Linux kernel page-table handling denial-of-service vulnerability.
Denial-of-service flaw in page-table handling caused by a poisoned PTE.
Linux kernel denial-of-service flaw in follow_page_pte() caused by a poisoned PTE entry.
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.