CVE-2026-49428 is a local kernel memory-safety vulnerability in FreeBSD's handling of POSIX largepage shared memory objects. Certain system calls, including open(2) when invoked with O_TRUNC and fspacectl(2), could incorrectly free memory associated with largepage objects even though those operations are not permitted for such objects. The implementation failed to verify that the target object type disallowed these operations, resulting in an invalid free and a subsequent use-after-free condition in kernel memory management. An unprivileged local user may trigger the flaw and gain access to freed kernel memory, creating a path to privilege escalation.
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 largepage handling vulnerability that can cause use-after-free conditions and may enable local privilege escalation.
A FreeBSD kernel memory-management vulnerability involving largepage handling that can lead to use-after-free conditions.
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.