Home / mailings FreeBSD Security Advisory FreeBSD-SA-26:93.tcp
Posted on 18 November 2026
FreeBSD security notificat=============================================================================FreeBSD-SA-26:93.tcp Security Advisory
The FreeBSD Project
Topic: Local privilege escalation via TCP MSG_OOB handling
Category: core
Module: tcp
Announced: 2026-11-17
Credits: OpenAI Security Research Team
Affects: All supported versions of FreeBSD.
Corrected: 2026-11-17 17:06:19 UTC (stable/15, 15.2-STABLE)
2026-11-17 17:08:36 UTC (releng/15.1, 15.1-RELEASE-p7)
2026-11-17 17:03:06 UTC (stable/14, 14.5-STABLE)
2026-11-17 17:05:28 UTC (releng/14.5, 14.5-RELEASE-p4)
2026-11-17 17:04:31 UTC (releng/14.4, 14.4-RELEASE-p13)
CVE Name: CVE-2026-127748
For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit <URL:https://security.FreeBSD.org/>.
I. Background
TCP supports a limited form of out-of-band data through its urgent
mechanism. A sender marks a byte as urgent using the MSG_OOB flag of
send(2), and the receiver can retrieve it separately from the normal data
stream using the MSG_OOB flag of recv(2).
II. Problem Description
When a segment carrying urgent data was received, tcp_pulloutofband()
removed the urgent byte by modifying the received data in place, without
checking whether the underlying buffer was writable. For example, when a
local sender used sendfile(2), the data could reference the cached pages
of the file being sent.
III. Impact
An unprivileged local user can exploit this to modify the cached contents
of files they are only permitted to read, and thereby obtain superuser
privileges.
IV. Workaround
No workaround is available.
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.
[FreeBSD 15.x]
# fetch https://security.FreeBSD.org/patches/SA-26:93/tcp-15.patch
# fetch https://security.FreeBSD.org/patches/SA-26:93/tcp-15.patch.asc
# gpg --verify tcp-15.patch.asc
[FreeBSD 14.x]
# fetch https://security.FreeBSD.org/patches/SA-26:93/tcp-14.patch
# fetch https://security.FreeBSD.org/patches/SA-26:93/tcp-14.patch.asc
# gpg --verify tcp-14.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
<URL:https://www.FreeBSD.org/handbook/kernelconfig.html> 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/ ae0f27b235b8 stable/15-n286889
releng/15.1/ ba88f842d665 releng/15.1-n283693
stable/14/ ab3b12345dd1 stable/14-n275594
releng/14.5/ c1eacc1471ad releng/14.5-n274929
releng/14.4/ 92b0ec051d7e releng/14.4-n273830
- -------------------------------------------------------------------------
Run the following command to see which files were modified by a
particular commit:
# git show --stat <commit hash>
Or visit the following URL, replacing NNNNNN with the hash:
<URL:https://cgit.freebsd.org/src/commit/?id=NNNNNN>
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
<URL:https://www.cve.org/CVERecord?id=CVE-2026-127748>
The latest revision of this advisory is available at
<URL:https://security.FreeBSD.org/advisories/FreeBSD-SA-26:93.tcp.asc>
