Loading vulnerability…
CVE-2026-49418 is a FreeBSD kernel virtual memory flaw in the device pager page-list handling for unmanaged device objects. When msync(MS_INVALIDATE) is invoked on a mapping of an unmanaged device object, the physical pages in the affected mapping range are marked invalid but are not removed from the pager's page list. A subsequent page fault can cause the fault handler to re-insert the page into the object's list, corrupting the list state. When the object is later destroyed, the corrupted bookkeeping can result in the same page being freed twice, producing a use-after-free / double-free condition in kernel memory management. FreeBSD describes the issue as reachable by an unprivileged local user and tied to memory/object invalidation behavior exposed through msync(MS_INVALIDATE).
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A FreeBSD memory invalidation flaw involving msync(MS_INVALIDATE) that may permit privilege escalation.
A race condition in FreeBSD memory-mapping handling involving msync(MS_INVALIDATE).
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.