Skip to main content
Mallory
HighVulnerability

CVE-2026-5398: FreeBSD TIOCNOTTY Use-After-Free Privilege Escalation

Published Apr 22, 2026 · Updated 27 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.4High · v3.1
EPSS0.21%11th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Freebsd
IdentifiersCVE-2026-5398CWE-416 · Use After Free

CVE-2026-5398 is a kernel use-after-free vulnerability in the FreeBSD TIOCNOTTY ioctl handler, affecting all supported FreeBSD versions at disclosure. TIOCNOTTY allows a process to detach from its controlling terminal, but the vulnerable implementation fails to clear a back-pointer from the terminal structure to the calling process's session. If the invoking process subsequently exits and the session memory is freed, the terminal structure can retain a dangling pointer. A malicious unprivileged local process can exploit this condition to obtain root privileges.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation permits local privilege escalation to root, compromising system confidentiality, integrity, and availability. An attacker gaining root privileges can access protected data, modify system state, and disrupt services.

Mitigation

If you can’t patch tonight, do this now.

No workaround is available. Installing the corrected kernel and rebooting is required to resolve the vulnerability.

Remediation

Patch, then assume compromise.

Apply the fixes released for FreeBSD-SA-26:10.tty on April 21, 2026, by upgrading to a supported stable or release/security branch containing the correction, then reboot. Fixes were issued for stable/15, stable/14, stable/13, and the release/security branches for FreeBSD 15.0, 14.4, 14.3, and 13.5. Use the applicable base-system package update or freebsd-update mechanism, or apply the official source patch, rebuild and install the kernel, and reboot.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FreebsdFreebsdoperating_system
FAQ

Frequently asked questions

Is CVE-2026-5398 exploited in the wild?
As of Oct 23, 2026, Mallory has no reports of CVE-2026-5398 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-5398?
As of Oct 23, 2026, Mallory has found no public exploit for CVE-2026-5398.
Is there a patch for CVE-2026-5398?
Apply the fixes released for FreeBSD-SA-26:10.tty on April 21, 2026, by upgrading to a supported stable or release/security branch containing the correction, then reboot. Fixes were issued for stable/15, stable/14, stable/13, and the release/security branches for FreeBSD 15.0, 14.4, 14.3, and 13.5.
What products are affected by CVE-2026-5398?
Freebsd.
How severe is CVE-2026-5398?
CVE-2026-5398 has a CVSS v3.1 score of 8.4 (High) and an EPSS score of 0.21% (11th percentile) as of Oct 23, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity7Community discussion across Reddit, Mastodon, and other social sources.