CVE-2026-63879 affects the Linux kernel AMDGPU driver's amdgpu_hmm_range_get_pages function. Reading the notifier sequence more than once can cause the page-handling logic to operate on invalid pages. The fix reads the notifier sequence only once, preventing inconsistent sequence handling. Invalid page use can potentially cause memory-safety issues or kernel instability; specific attacker-controlled exploitation outcomes have not been established.
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.
22 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability in amdgpu_hmm_range_get_pages within the Linux kernel AMDGPU driver. The content does not provide the underlying defect or security impact.
A vulnerability covered by the Miracle Linux kernel package update. Individual technical details and exploit availability are not specified.
A vulnerability addressed by the Miracle Linux AXSA-2026-1750 kernel-related package update; the technical flaw details are not provided.
A vulnerability addressed by the AlmaLinux 9 kernel update; no vulnerability-specific technical details are supplied.
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.