Skip to main content
Mallory
UnratedVulnerability

CVE-2026-101313: FreeBSD KTLS control-message out-of-bounds read

Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days3 mentions · peak 2 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-101313CWE-125

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.

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.

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.

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.
FAQ

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.
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 activityCommunity discussion across Reddit, Mastodon, and other social sources.