-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ============================================================================= FreeBSD-SA-26:79.nfs Security Advisory The FreeBSD Project Topic: NFSv4 server remote code execution via stateid type confusion Category: core Module: nfsserver Announced: 2026-11-17 Credits: H. P. Cook Affects: All supported versions of FreeBSD. Corrected: 2026-11-17 17:05:53 UTC (stable/15, 15.2-STABLE) 2026-11-17 17:08:09 UTC (releng/15.1, 15.1-RELEASE-p7) 2026-11-17 17:02:46 UTC (stable/14, 14.5-STABLE) 2026-11-17 17:05:08 UTC (releng/14.5, 14.5-RELEASE-p4) 2026-11-17 17:04:11 UTC (releng/14.4, 14.4-RELEASE-p13) CVE Name: CVE-2026-101317 For general information regarding FreeBSD Security Advisories, including descriptions of the fields above, security branches, and the following sections, please visit . I. Background The Network File System (NFS) allows a host to export file systems so that other hosts can mount them over the network. NFS version 4 (NFSv4) servers track per-client state, such as open files, byte-range locks and delegations, each identified by a stateid. A delegation allows a client to open, lock and cache a file locally without contacting the server, until the server recalls it. Clients release delegations using the DELEGRETURN operation. II. Problem Description When processing a DELEGRETURN operation, the NFSv4 server did not verify that the supplied stateid referred to a delegation. A client could supply an open or lock stateid instead, causing the server to free that state while it was still referenced, resulting in a use-after-free. III. Impact A remote NFSv4 client which is able to open a file on an exported file system can corrupt kernel memory on the server, causing a kernel panic or potentially executing arbitrary code in the kernel. IV. Workaround No workaround is available, but systems not acting as NFSv4 servers are not affected. NFSv4 service is disabled by default; the following command, run on the host and in any vnet jail running nfsd(8), prints 4 if it is enabled: # sysctl -n vfs.nfsd.server_max_nfsvers 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:79/nfs.patch # fetch https://security.FreeBSD.org/patches/SA-26:79/nfs.patch.asc # gpg --verify nfs.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/ d1ffacacaad3 stable/15-n286864 releng/15.1/ 2b58bfa57245 releng/15.1-n283667 stable/14/ b04070ee6f3f stable/14-n275575 releng/14.5/ 41df8a74ee29 releng/14.5-n274910 releng/14.4/ 5a28955eeff3 releng/14.4-n273811 - ------------------------------------------------------------------------- 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----- iQJPBAEBCgA5FiEEthUnfoEIffdcgYM7bljekB8AGu8FAmr82jsbFIAAAAAABAAO bWFudTIsMi41KzEuMTIsMCwzAAoJEG5Y3pAfABrvRxgP/inJcMeSrmhJLAZ+Ov+I jvpfYgD5ej5hkE13HFHpEVA2ohHYO7uB/JpJADfwkJFyzBaDW2axtNycqWhHl8sB 3jZZiKi5s/S2M7jOHGqHHySDwrpMV3duPFGZUaJX+kTQgV/kO7GPPWxpxLjKVzoM heotlv0ZJkC2HeT8zTMmR4UM8W3JU/psGxN5geZMFYyyWzWaDqpJllXq4VgVLBD7 ZZyj+EeeCMBQq1YOYWsJ2VBMgUDp4FnuVdHV83T3stfC5RS6IQ0glbm6vfIylUm+ NVL2UPPWyXMJBdqWB/x6PXwDjx+MsovTnuiJ5xdmcW1KY84f3QhzBxAXLAJ8bozR 4RWQPuj2ACfj2v1si6vSbYT2Ub8DgmAjZ4gl8GThbv72jN0QWB11gsupGF91LBW9 sI2VGrRbtRu6zQXR/HI/QvLYsOyonp7LgjvaPboQDvz+fWGv7R5IbbYOG2VfQENK Zamv9EiSU0+12eLqgQUVkVDVAzY01X+wOlSydgnp5X69U0UEHfPOldjQtPLKIxww +Qcw09l/zRnxnqOppu9CMxujEsD6Mq6DahcHbqYoi7wK1I6rqm3EiYbIyBmGPbiq ombPv/9BF2pmoBDakg89NLHgx5qbJQSQmV7+XaoKLoLGSFf4bp7FKfKd4+nvKYrw +fds5mub1ZivILzaO3psH8fZ =KxY+ -----END PGP SIGNATURE-----