-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ============================================================================= FreeBSD-SA-26:87.socket Security Advisory The FreeBSD Project Topic: Privilege escalation via socket unsplice timeout Category: core Module: socket Announced: 2026-11-17 Credits: OpenAI Security Research Team Affects: All supported versions of FreeBSD. Corrected: 2026-11-17 17:06:07 UTC (stable/15, 15.2-STABLE) 2026-11-17 17:08:25 UTC (releng/15.1, 15.1-RELEASE-p7) 2026-11-17 17:02:54 UTC (stable/14, 14.5-STABLE) 2026-11-17 17:05:17 UTC (releng/14.5, 14.5-RELEASE-p4) 2026-11-17 17:04:19 UTC (releng/14.4, 14.4-RELEASE-p13) CVE Name: CVE-2026-127740 For general information regarding FreeBSD Security Advisories, including descriptions of the fields above, security branches, and the following sections, please visit . I. Background The SO_SPLICE socket option, set with setsockopt(2), splices two TCP sockets together so that the kernel forwards data received on one socket to the other without userspace intervention. A splice may be configured with an idle timeout, after which the kernel removes it automatically. II. Problem Description When a splice's idle timeout expired, the kernel unspliced the source socket without verifying that the socket still belonged to that splice. If another thread had meanwhile unspliced the socket and spliced it again, the timeout handler could tear down the new splice instead, resulting in a use-after-free. Concurrent teardowns of a splice after an error were similarly unserialized. III. Impact An unprivileged local user may be able to exploit the use-after-free to escalate 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.1] # fetch https://security.FreeBSD.org/patches/SA-26:87/socket-15.patch # fetch https://security.FreeBSD.org/patches/SA-26:87/socket-15.patch.asc # gpg --verify socket-15.patch.asc [FreeBSD 14.5] # fetch https://security.FreeBSD.org/patches/SA-26:87/socket-14.5.patch # fetch https://security.FreeBSD.org/patches/SA-26:87/socket-14.5.patch.asc # gpg --verify socket-14.5.patch.asc [FreeBSD 14.4] # fetch https://security.FreeBSD.org/patches/SA-26:87/socket-14.4.patch # fetch https://security.FreeBSD.org/patches/SA-26:87/socket-14.4.patch.asc # gpg --verify socket-14.4.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/ 6ace2eb40b44 stable/15-n286878 releng/15.1/ de7f7d5ea959 releng/15.1-n283682 stable/14/ 37ccdca189ca stable/14-n275583 releng/14.5/ ec58c6a8ca80 releng/14.5-n274918 releng/14.4/ cededaef8357 releng/14.4-n273819 - ------------------------------------------------------------------------- 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----- iQJPBAEBCgA5FiEEthUnfoEIffdcgYM7bljekB8AGu8FAmr82lEbFIAAAAAABAAO bWFudTIsMi41KzEuMTIsMCwzAAoJEG5Y3pAfABrv838P/2O2lvvDg4m5vanyRj1H MdxwrXwVHuZRjDkvCdzuiINq5uT8ZSJngOiOEYBFlQZEtXEbLiAOsOU3ZCsp11ND oxIF1b3h5FappGk2MTICZr6nsEdwgxpACed3XQDEA2y3+Xi+MXYa5L25R3Kmk1m0 GNRkd+Ebh/KLHXO5+2EYX+Iv1bahmbcoPUPb6JOqPa1PMU+75ohGCapuD5Qq7GMZ 8BOzSHrZ5kcJqC/uxcXbnq5U/IRWKRQ7qX1SUO3D99edpnwHfCJWkBzaU0Doecw1 e5a7D9TJAMGATtFBPwXeKW2KqIcBF7LXBwq1Hqxe+xuTFm9rFF3HIAwfMLoXyP6L 1GNeq+e28EnEu4iUyjXCKl1/v7Vgr7jsjjVTPRJVOc5ZMAKFCQJTWCFh3SskPMb7 fJ6ODNN83AlFIlsmBY9JU7XhFe4u0YSjM+9+PKJLE7WA3W/GxI6bh3sC49U36oqw w3yMzANJAXallVI48+tGapb09rVLKMwW2Er+hFVBpFfnKi7JIjJ3SVJc+FjIqgl8 nd5/WSc4FbLoK2K9bB9FMA9BcIhdkdfbhXGTnYeKv17wKPQzq4fol9WXur55/amB er/sn2QhvHUmZQdxV41kqEsS0/2UvtnZwK3MEWsGbDPbVYUeDirtyBFuVqbEY3Zs uVJR7GNKzR5eQGs2V3uwPa+7 =e6gY -----END PGP SIGNATURE-----