CVE-2026-101313: FreeBSD KTLS control-message out-of-bounds read
CVE-2026-101313 is an information-disclosure vulnerability in the FreeBSD kernel's sosend_generic() function when KTLS is enabled. Insufficient length validation allows a TLS_SET_RECORD_TYPE control message containing only a cmsghdr, without its required one-byte payload, to pass the size check. The kernel consequently reads one byte beyond the control message and uses that uninitialized kernel-memory byte as the outgoing TLS record type. On TLS 1.2 connections, the byte is exposed in the plaintext record header. All supported FreeBSD versions preceding their respective corrections are affected when KTLS is enabled.
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.
A local, low-privileged user can disclose one byte of uninitialized kernel memory through an outgoing TLS 1.2 record header. No integrity or availability impact is identified.
Mitigation
If you can’t patch tonight, do this now.
Disable KTLS by running sysctl kern.ipc.tls.enable=0. Systems with kern.ipc.tls.enable set to 0 are not affected; this workaround disables KTLS entirely.
Remediation
Patch, then assume compromise.
Upgrade to a corrected FreeBSD branch or release: 15.2-STABLE, 15.1-RELEASE-p7, 14.5-STABLE, 14.5-RELEASE-p4, 14.4-RELEASE-p13, or a later patched version, then reboot. For applicable amd64 or arm64 installations using base system packages on FreeBSD 15.0-RELEASE or later, run pkg upgrade -r FreeBSD-base. For RELEASE installations using binary distribution sets on amd64 or arm64, run freebsd-update fetch followed by freebsd-update install. Alternatively, verify and apply the official source patch, rebuild the kernel, and reboot.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-101313 exploited in the wild?
- As of Nov 19, 2026, Mallory has no reports of CVE-2026-101313 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-101313?
- As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-101313.
- Is there a patch for CVE-2026-101313?
- Upgrade to a corrected FreeBSD branch or release: 15.2-STABLE, 15.1-RELEASE-p7, 14.5-STABLE, 14.5-RELEASE-p4, 14.4-RELEASE-p13, or a later patched version, then reboot. For applicable amd64 or arm64 installations using base system packages on FreeBSD 15.0-RELEASE or later, run pkg upgrade -r FreeBSD-base.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.