CVE-2026-49419 is a FreeBSD Jail subsystem vulnerability caused by incorrect reference-count handling in kern_jail_set() and kern_jail_get() when the JAIL_AT_DESC flag is used. The code releases the reference to the caller's current prison before attempting jail descriptor lookup; if that lookup fails, the error-handling path releases the same reference a second time. This double release causes a prison reference count underflow and can result in the prison structure being freed while still in active use, creating a kernel memory-safety condition consistent with a use-after-free scenario. The flaw is reachable through jail_set and jail_get operations and can be triggered by an unprivileged local user.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An underflow vulnerability in FreeBSD Jail handling that may permit privilege escalation from a jail context via jail_set/jail_get operations.
An integer underflow vulnerability in FreeBSD's Jail subsystem that may allow memory corruption or privilege-impacting behavior via jail_set/jail_get operations.
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.