Loading vulnerability…
CVE-2026-5398 is a kernel use-after-free vulnerability in FreeBSD's handling of the TIOCNOTTY ioctl(2) operation, which allows a process to detach from its controlling terminal. The flaw is caused by the TIOCNOTTY implementation failing to clear a back-pointer from the controlling terminal structure to the calling process's session. If the invoking process subsequently exits, the terminal structure can retain a pointer to freed session memory, leaving a dangling pointer in the kernel tty subsystem. A malicious process can then abuse this stale kernel pointer to obtain root privileges.
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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A FreeBSD local privilege escalation vulnerability caused by a dangling pointer/use-after-free condition in the TIOCNOTTY implementation, allowing a malicious local process to potentially gain root privileges.
A FreeBSD kernel TIOCNOTTY use-after-free vulnerability that can allow a malicious process to escalate privileges to root.
A local privilege escalation vulnerability in the FreeBSD kernel's TIOCNOTTY handler caused by a use-after-free/dangling pointer condition, allowing an unprivileged malicious process to potentially gain root privileges.
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.