-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ============================================================================= FreeBSD-SA-26:86.freebsd32 Security Advisory The FreeBSD Project Topic: Privilege escalation via compat32 recvmsg(2) control messages Category: core Module: freebsd32 Announced: 2026-11-17 Credits: OpenAI Security Research Team Affects: All supported versions of FreeBSD. Corrected: 2026-11-17 17:06:06 UTC (stable/15, 15.2-STABLE) 2026-11-17 17:08:23 UTC (releng/15.1, 15.1-RELEASE-p7) 2026-11-17 17:02:51 UTC (stable/14, 14.5-STABLE) 2026-11-17 17:05:14 UTC (releng/14.5, 14.5-RELEASE-p4) 2026-11-17 17:04:15 UTC (releng/14.4, 14.4-RELEASE-p13) CVE Name: CVE-2026-101321 For general information regarding FreeBSD Security Advisories, including descriptions of the fields above, security branches, and the following sections, please visit . I. Background The compat32 subsystem allows 32-bit binaries to run on 64-bit platforms. System calls whose parameters require translation are handled by compat32 before being dispatched to the native system call handler. This includes control messages received with recvmsg(2), whose layout differs between the 32-bit and 64-bit ABIs. II. Problem Description When copying received control messages out to a 32-bit process, compat32 temporarily modified the length field of each message header in place. When a large control message was read with the MSG_PEEK flag, its storage remained shared with the socket buffer, so this modification could race with concurrent operations on the same socket and corrupt the socket's queue of messages. III. Impact An unprivileged local user can exploit the resulting memory corruption to escalate privileges. IV. Workaround No workaround is available. Kernels compiled without the COMPAT_FREEBSD32 configuration option are not affected. 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:86/freebsd32.patch # fetch https://security.FreeBSD.org/patches/SA-26:86/freebsd32.patch.asc # gpg --verify freebsd32.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/ 9a38d35b14bc stable/15-n286877 releng/15.1/ ae141340011e releng/15.1-n283680 stable/14/ 0c5fdfa72f09 stable/14-n275580 releng/14.5/ 46fcdeb6cdad releng/14.5-n274915 releng/14.4/ 4cbd89510ee2 releng/14.4-n273815 - ------------------------------------------------------------------------- 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----- iQJPBAEBCgA5FiEEthUnfoEIffdcgYM7bljekB8AGu8FAmr82k4bFIAAAAAABAAO bWFudTIsMi41KzEuMTIsMCwzAAoJEG5Y3pAfABrvw74QAL0Zp8XkBK9oiA3JB3DD d1DuLiIcYv4GlxP+fSEb0djGyE8ZivngqrlqswEczVgG7ipTwMwbBUn0paLtG/35 zmpW0S6pLAoNmFj2itNV1+Q5rmWeWnbhjEC/2ow42Fp5XObcmDSCIKYJEMJQ5aH3 1+5/aUgRlvcn2v9DMv+D1gklkMicUv8NZqjGOHdzB6LRerPB9G9iSnVqIQHrbREi YXJsa1IQZaenZanG3BeOWmh/zNSHTWM05joCJvA65vE0O4N8RKagOghOsSycw2ZI FlIMstx2GjNT3UvTbTpkNOE0HAucwO0iqLTCcPWWGrUX7od7fpS+fe77e7GBSZSN MekqlPO/78sDlkCx+RLoJqzX3vf55c4a0Cs6d+Ql1oW9I1RmSqJzaaPgKVAeWfPe LCRQunFDottN6pT/TSEeffnzgwiAuKailAegIkI1TgwgiVuy0u6CRsAKNKMJuG3p OZctjfz2vn8qNEQg5mDOMFvQ9nXY8UZAYPVfAtHiNgeXCg7giC30FKMaDhFDqHPP 07p+iJSCuRdWfMzJRrBbw46W+kWqP3BAJuf/4q20p9MHsr48Vz3pB5MVetdPcmNG xBmhNfT41ch1lQHewsD4+Ky24AqdUbkrZMQ1pIBQQ16iYQODjAixAA0n6pHr1Z1U ZfYhmqheO8HAsn1e9mIegvr6 =pPoJ -----END PGP SIGNATURE-----