-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
=============================================================================
FreeBSD-SA-26:94.tmpfs Security Advisory
The FreeBSD Project
Topic: tmpfs(4) fails to clear set-group-ID bit on new files
Category: core
Module: tmpfs
Announced: 2026-11-17
Credits: Kevin Day
Affects: All supported versions of FreeBSD.
Corrected: 2026-11-17 17:06:21 UTC (stable/15, 15.2-STABLE)
2026-11-17 17:08:38 UTC (releng/15.1, 15.1-RELEASE-p7)
2026-11-17 17:03:08 UTC (stable/14, 14.5-STABLE)
2026-11-17 17:05:30 UTC (releng/14.5, 14.5-RELEASE-p4)
2026-11-17 17:04:33 UTC (releng/14.4, 14.4-RELEASE-p13)
CVE Name: CVE-2026-127749
For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit .
I. Background
tmpfs(4) is a memory-backed file system. New files inherit the group of
the directory in which they are created. To prevent users from creating
set-group-ID files for groups they do not belong to, the kernel clears
the set-group-ID bit of a new file if its creator is not a member of the
file's group.
II. Problem Description
tmpfs(4) did not clear the set-group-ID bit when a file was created by a
user who was not a member of the file's group.
III. Impact
An unprivileged local user with write access to a tmpfs(4) directory
owned by a group they do not belong to can create a set-group-ID
executable for that group, and so gain that group's privileges. For
example, where /tmp is a tmpfs(4) mount, any local user can obtain the
privileges of the wheel group, which owns /tmp.
IV. Workaround
No workaround is available, but systems without tmpfs(4) mounts are not
affected. Mounting tmpfs(4) file systems with the nosuid option prevents
set-group-ID executables on them from taking effect, for example:
# mount -u -o nosuid /tmp
To make the change persistent, add the nosuid option to the file system's
entry in /etc/fstab.
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:94/tmpfs-15.patch
# fetch https://security.FreeBSD.org/patches/SA-26:94/tmpfs-15.patch.asc
# gpg --verify tmpfs-15.patch.asc
[FreeBSD 14.x]
# fetch https://security.FreeBSD.org/patches/SA-26:94/tmpfs-14.patch
# fetch https://security.FreeBSD.org/patches/SA-26:94/tmpfs-14.patch.asc
# gpg --verify tmpfs-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
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/ eb4482d1cc55 stable/15-n286891
releng/15.1/ 4b3e04519281 releng/15.1-n283695
stable/14/ 207239d68948 stable/14-n275596
releng/14.5/ 24e39556f90f releng/14.5-n274931
releng/14.4/ 27ce018206b2 releng/14.4-n273832
- -------------------------------------------------------------------------
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-----
iQJPBAEBCgA5FiEEthUnfoEIffdcgYM7bljekB8AGu8FAmr82mgbFIAAAAAABAAO
bWFudTIsMi41KzEuMTIsMCwzAAoJEG5Y3pAfABrvWzQP/0K74Y9kVt42v2VoQm4o
D6rMVbtu7vTzGgRBK+KjyN4PxA+0gh5Tg+yr8585WCIlF9wW5x+YcR3APMfFrQDA
dFuDSNTxNxzojNx8Ky7mISOWLlXyb3YXS98yqrQtABfByTNYO2e87iTv0QIUTnXo
G1y/P+ENjfOY/o8W3Fwxi0h3F4kUfNcSpwL5EK81/sy0yUwF7EI98I8iw259UKru
uBOmkkTgFaKnrdu13llzPBVcy5CcTiQfMvhBplF0ckZjHE1bwdr51GQXmZfF461r
uzDqoxbDFMXlKXF4Dpn1z+GNvmLGQmorweaqYTdTFg/TVy/hBo2JW9byGJ2ynK8c
bNiflVu03gN+LCEoWmZoLrDNtsz9LtRx+/qL+1dxSpjTI3nxgKWylKdpkP8iPdfr
F7xmi3S6bticIkP8g6Zai6QYvk6jkhx0o6G/ql0TGZG/J0ZlShieOIsZkthxOXS/
oOUemKqACKJlH867qdb+7aFRewi/t5fSL0sxLMr4BMSGZlIUjeMsO2H3tZa3SRw3
my3tIkbqbFHqGkA8eXkJC7v2gDB3nB2nPloJaxYUgo85ELdtDjGFhZEyd8HwPqdX
Gw5PtNCBU308K3MNGPV+2/pv8OA+IHRt4m2vSYwRJrgre9ihcmLe41OhspY75Leu
f0sR8gW+xD6/235O1SSIbRJ+
=cpvj
-----END PGP SIGNATURE-----