Skip to main content
Mallory
Unrated

FreeBSD kTLS-RX arbitrary file overwrite local privilege escalation

IdentifiersCVE-2026-45257CWE-123

CVE-2026-45257 is a local privilege escalation vulnerability in FreeBSD’s Kernel TLS (kTLS) receive path. The flaw arises from unsafe interaction between sendfile(2), unprivileged TCP_RXTLS_ENABLE, and in-place AES-GCM decryption on vnode-backed M_EXTPG/EXTPG mbufs. In the vulnerable path, sendfile(2) can produce mbufs whose page references point directly at the backing page-cache pages of a readable file. An unprivileged user can then enable kTLS receive on a TCP socket they control, send the file over a loopback connection, and cause in-place decryption to operate on those file-backed pages through the kernel direct map (DMAP). Because the attacker controls the TLS keying material and knows the original file contents, they can choose the resulting plaintext bytes written into the page-cache page. The write bypasses normal VFS-mediated permission enforcement and can affect any file the attacker can read. Reported affected versions include FreeBSD 13.0 through 13.4, 14.0 through 14.2, and 15.0-RELEASE; FreeBSD 12.x and earlier are reported as not affected. MidnightBSD 4.0+ was also noted as impacted.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

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

Successful exploitation allows an unprivileged local user to overwrite attacker-chosen bytes in trusted files they can read, including setuid-root binaries, resulting in reliable local root privilege escalation. The overwrite bypasses file permissions, mount options, and immutable flags such as schg because the corruption occurs via page-cache pages through DMAP rather than through the normal VFS write path. The issue can also cause persistent on-disk corruption, particularly on UFS, creating integrity and persistence risks beyond immediate privilege escalation.

Mitigation

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

No workaround is available according to the FreeBSD advisory.

Remediation

Patch, then assume compromise.

Upgrade to a corrected FreeBSD supported stable or release/security branch containing the vendor fix and reboot. Supported remediation paths cited by the vendor include using freebsd-update for binary distribution sets, pkg upgrade for base system packages where applicable, or applying the official patch from the FreeBSD advisory (FreeBSD-SA-26:26.kTLS / https://security.FreeBSD.org/patches/SA-26:26/ktls.patch), rebuilding the kernel, and rebooting.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

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
FreebsdFreebsdapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

8 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

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, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity7

Community discussion across Reddit, Mastodon, and other social sources.