-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ============================================================================= FreeBSD-SA-26:74.ktls Security Advisory The FreeBSD Project Topic: Kernel memory disclosure via KTLS control messages Category: core Module: ktls Announced: 2026-11-17 Credits: Olivier Cochard-Labbé Affects: All supported versions of FreeBSD. Corrected: 2026-11-12 19:15:39 UTC (stable/15, 15.2-STABLE) 2026-11-17 17:08:02 UTC (releng/15.1, 15.1-RELEASE-p7) 2026-11-12 17:52:38 UTC (stable/14, 14.5-STABLE) 2026-11-17 17:05:02 UTC (releng/14.5, 14.5-RELEASE-p4) 2026-11-17 17:04:04 UTC (releng/14.4, 14.4-RELEASE-p13) CVE Name: CVE-2026-101313 For general information regarding FreeBSD Security Advisories, including descriptions of the fields above, security branches, and the following sections, please visit . I. Background Kernel TLS (KTLS) moves Transport Layer Security (TLS) record processing into the kernel, allowing applications to encrypt and decrypt socket data without copying it to and from userspace and to serve TLS data with sendfile(2). Applications using KTLS on the transmit path may specify the TLS record type for each outgoing record via a TLS_SET_RECORD_TYPE control message passed to sendmsg(2). II. Problem Description The code in sosend_generic() which parses TLS_SET_RECORD_TYPE control messages failed to verify that the message was large enough to hold its one-byte payload. A control message containing only a cmsghdr would pass the size check, causing the kernel to read one byte past the end of the message and use it as the TLS record type. III. Impact A local user with a KTLS-enabled socket can send a crafted TLS_SET_RECORD_TYPE control message to cause the kernel to read one byte of uninitialized kernel memory and use it as the TLS record type in an outgoing TLS record. For TLS 1.2 connections, the record type is visible in the plaintext record header, constituting a kernel information disclosure. IV. Workaround Systems with the kern.ipc.tls.enable sysctl set to 0 are not affected. Setting it to 0 disables KTLS entirely: # sysctl kern.ipc.tls.enable=0 V. Solution Upgrade your vulnerable system to a supported FreeBSD stable or release / security branch (releng) dated after the correction date, and reboot the system. Perform one of the following: 1) To update your vulnerable system installed from base system packages: Systems running a 15.0-RELEASE or later version of FreeBSD on the amd64 or arm64 platforms, which were installed using base system packages, can be updated via the pkg(8) utility: # pkg upgrade -r FreeBSD-base # shutdown -r +10min "Rebooting for a security update" 2) To update your vulnerable system installed from binary distribution sets: Systems running a RELEASE version of FreeBSD on the amd64 or arm64 platforms which were not installed using base system packages can be updated via the freebsd-update(8) utility: # freebsd-update fetch # freebsd-update install # shutdown -r +10min "Rebooting for a security update" 3) To update your vulnerable system via a source code patch: The following patches have been verified to apply to the applicable FreeBSD release branches. a) Download the relevant patch from the location below, and verify the detached PGP signature using your PGP utility. # fetch https://security.FreeBSD.org/patches/SA-26:74/ktls.patch # fetch https://security.FreeBSD.org/patches/SA-26:74/ktls.patch.asc # gpg --verify ktls.patch.asc b) Apply the patch. Execute the following commands as root: # cd /usr/src # patch -E -p0 < /path/to/patch c) Recompile your kernel as described in and reboot the system. VI. Correction details This issue is corrected as of the corresponding Git commit hash in the following stable and release branches: Branch/path Hash Revision - ------------------------------------------------------------------------- stable/15/ 42e7802e24fe stable/15-n286742 releng/15.1/ 5163206d9fe9 releng/15.1-n283660 stable/14/ f279c33cef3c stable/14-n275509 releng/14.5/ ffb23d0f6c67 releng/14.5-n274904 releng/14.4/ 31ae088f4ace releng/14.4-n273805 - ------------------------------------------------------------------------- Run the following command to see which files were modified by a particular commit: # git show --stat Or visit the following URL, replacing NNNNNN with the hash: To determine the commit count in a working tree (for comparison against nNNNNNN in the table above), run: # git rev-list --count --first-parent HEAD VII. References The latest revision of this advisory is available at -----BEGIN PGP SIGNATURE----- iQJPBAEBCgA5FiEEthUnfoEIffdcgYM7bljekB8AGu8FAmr82iwbFIAAAAAABAAO bWFudTIsMi41KzEuMTIsMCwzAAoJEG5Y3pAfABrvixMP/iBl0122SFpjULIe04AS I2+NRh3j2TXUFnzEchstNwbijhUTd0edIK0/nk9EV+gF2tNdMRERUh732EctwE9b LSDsvCYWssTweEaQP60D4ExRrqV5O20Er0ebd3C2sw/W7jML61LSNCGVX1J0ZnTb 3OmSEOW+6FmUoQC16KfuTDovlYfg9uOaU3CZ9ZdRwIEYcnPAefPmgnRVRPheZvzw xkSTL1lsPujYvSjdBqP6LO23044pYbHNB+Lu+jEDyg+mU1deKC35+5INDVXvjbEH qYwciKFbJDD3B/nRvVMr8CdOO2dKeWHdBIhldz0ji9uEtV3bqZ50PariUTnCSAVm Elv8MSy7tQmgcNd7xbfVNfqAl14s1U/mKbts0/OyUvpVNhJx6Dt6QIG6F+AFIePS GMMScIeyCoMs9si/hnziFykfWINe/lX67g+BzFzNhZ26WmKkmbO8808n6DZcOE86 4NO6ggBh4w6P2g3F1AnOdEeeCgru+hBnl81fX5oJMlT97RO/NUxHxgrI+P/QPv9S kOzx+Osp0EW6WAJq7/GP2KbAAVQh/ZD/r2S4SSdCvNsLuMxxPPngzFtjtZMFV8My MwyHCK/LVBt4O9eSR80rgh6aDP+trdIyrL4O24cu9jTG9X2SH2i6SD5ez/lPYEIk uZNHRw5kHKZ+Mjug7kRtUqXw =7hcu -----END PGP SIGNATURE-----