-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ============================================================================= FreeBSD-SA-26:91.fdescfs Security Advisory The FreeBSD Project Topic: Privilege escalation via missing fdescfs(4) access checks Category: core Module: fdescfs Announced: 2026-11-17 Credits: Kevin Day Affects: All supported versions of FreeBSD. Corrected: 2026-11-17 17:06:17 UTC (stable/15, 15.2-STABLE) 2026-11-17 17:08:34 UTC (releng/15.1, 15.1-RELEASE-p7) 2026-11-17 17:03:04 UTC (stable/14, 14.5-STABLE) 2026-11-17 17:05:26 UTC (releng/14.5, 14.5-RELEASE-p4) 2026-11-17 17:04:28 UTC (releng/14.4, 14.4-RELEASE-p13) CVE Name: CVE-2026-127745 For general information regarding FreeBSD Security Advisories, including descriptions of the fields above, security branches, and the following sections, please visit . I. Background The file-descriptor file system, fdescfs(4), provides access to a process's open file descriptors through the file system namespace, conventionally at /dev/fd. For example, /dev/fd/3 refers to the file open on descriptor 3. fdescfs(4) is not mounted by default. II. Problem Description fdescfs(4) did not implement access checks for its files, and did not verify that a descriptor was open for writing before changing the size of the underlying file. As a result, truncate(2) on /dev/fd/N succeeded even when descriptor N was open read-only. fdescfs(4) also checked the wrong Capsicum rights on the descriptor when changing file attributes. III. Impact An unprivileged local user can truncate or extend any file which they are able to open for reading, including system files owned by root. This may allow privilege escalation or a Denial of Service (DoS). IV. Workaround No workaround is available, but systems without fdescfs(4) mounted, or with it mounted using the "nodup" option, are not affected. The following command lists fdescfs(4) mounts: # mount -t fdescfs 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:91/fdescfs.patch # fetch https://security.FreeBSD.org/patches/SA-26:91/fdescfs.patch.asc # gpg --verify fdescfs.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/ 223cce4e03e4 stable/15-n286887 releng/15.1/ 1a5557e16105 releng/15.1-n283691 stable/14/ d7fc010ca397 stable/14-n275592 releng/14.5/ 1e1ab955789a releng/14.5-n274927 releng/14.4/ fd307b451793 releng/14.4-n273828 - ------------------------------------------------------------------------- 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----- iQJPBAEBCgA5FiEEthUnfoEIffdcgYM7bljekB8AGu8FAmr82mAbFIAAAAAABAAO bWFudTIsMi41KzEuMTIsMCwzAAoJEG5Y3pAfABrvSR4P/1HVkw/0J0ZZo+1dEJXp o/rfKRLyyAExmQb3HHBEz/dIGBVQJoypErPv4IUjPFUTNLDbuMwENZPr/4qbXZqr jeQcGkTLA3KmU7jO/WsiUpO4qWs87mcVg755mj1jiHVhIibt+dDJvnhZ0Tp+B24X qMFRdHYS8rwSeGjHyNcGCS0xo9P0FD/kyEuxFaugJDPcmp4BkVJ91f/xtmIR3noM gQhurvAC4n9bgakQ8fOCi2srJuqRl5OfOZx/w9FNLIgJPwdeMaJIqSKPuZnhVAQK CMNi0klChWXSOByIKQS1irLV1vXQf+gTSMN8hsPA9RLpONDOJw6/xEANjyxcyZf9 CQpHIEBfGEY70x6gCSiIQSqiBt2crTLNj2OHslYtrKwlOvbCHfT00y2MLVMr87Pw TpZ7XDeuqfOgWv9rlvtggQ4a0AorYDq/3pGB0tYY37nFFNLwYckSgxfLOQ5cy4Lu k7v8O21ppJHt9i5saVufOWGzY/GgT3fAvEBhVqMfrJkxkdrTLQ51ltQx5JNz8wAi d9Fd+FvIwpwShjrdyfR1bIkhrYv7RIMRS8+fsH92q8JHGJPFaXvSur43OYvmm8PJ KU1zC3+TpqVZmQcnmmyhdBIwIl39TSLYqcY2/7pBn6X2hUGHtr6kkiM4R2jy5beF jPhpULSNg37Yn7/T7DDwFDKP =/XJE -----END PGP SIGNATURE-----