Loading vulnerability…
CVE-2025-39883 is a flaw in the Linux kernel mm/memory-failure subsystem. The unpoison_memory() path can evaluate the PG_HWPoison state of a page corresponding to an offline, uninitialized memory PFN. This triggers the VM_BUG_ON_PAGE(PagePoisoned(page)) assertion, resulting in an invalid-opcode kernel BUG and fatal kernel panic. The fix rejects the operation when pfn_to_online_page() returns NULL, preventing processing of offline or otherwise invalid pages in this path.
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 Linux kernel memory-failure handling flaw triggered while unpoisoning memory.
A Linux kernel vulnerability in the memory-failure handling code related to VM_BUG_ON_PAGE(PagePoisoned(page)) when unpoisoning memory.
A Linux kernel mm/memory-failure vulnerability involving VM_BUG_ON_PAGE(PagePoisoned(page)) during memory unpoisoning.
A Linux kernel memory-failure handling flaw triggered while unpoisoning memory pages.
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.