-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
=============================================================================
FreeBSD-SA-26:75.linux Security Advisory
The FreeBSD Project
Topic: Kernel memory disclosure via Linuxulator extattr syscalls
Category: core
Module: linux
Announced: 2026-11-17
Credits: Nick Price
Affects: All supported versions of FreeBSD.
Corrected: 2026-11-12 19:15:40 UTC (stable/15, 15.2-STABLE)
2026-11-17 17:08:03 UTC (releng/15.1, 15.1-RELEASE-p7)
2026-11-12 17:52:39 UTC (stable/14, 14.5-STABLE)
2026-11-17 17:05:03 UTC (releng/14.5, 14.5-RELEASE-p4)
2026-11-17 17:04:05 UTC (releng/14.4, 14.4-RELEASE-p13)
CVE Name: CVE-2026-101314
For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit .
I. Background
The Linux binary compatibility layer (Linuxulator) allows unmodified Linux
binaries to run on FreeBSD. It implements the Linux listxattr() family of
system calls, which return the names of a file's extended attributes.
II. Problem Description
The Linuxulator's listxattr() implementation sized its kernel buffer using
min(), which truncates its arguments to 32 bits. A 64-bit Linux process
could pass a size which yielded a small buffer while later bounds checks
used the full size. The code parsing the attribute list then read past the
end of the buffer and copied adjacent kernel memory to userspace.
III. Impact
An unprivileged local user can read kernel memory, which may contain
sensitive information, or trigger a kernel panic, resulting in a Denial of
Service (DoS).
IV. Workaround
No workaround is available, but systems without the 64-bit Linux binary
compatibility layer (linux64.ko) loaded are not affected. The following
command can be used to test whether it is loaded:
# kldstat -m linux64elf
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:75/linux.patch
# fetch https://security.FreeBSD.org/patches/SA-26:75/linux.patch.asc
# gpg --verify linux.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/ a46d6ae4c0b6 stable/15-n286743
releng/15.1/ 52fe4ad71f4b releng/15.1-n283661
stable/14/ fd57277fc3c2 stable/14-n275510
releng/14.5/ 3ed6964f2533 releng/14.5-n274905
releng/14.4/ 06a0f9a66be0 releng/14.4-n273806
- -------------------------------------------------------------------------
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-----
iQJPBAEBCgA5FiEEthUnfoEIffdcgYM7bljekB8AGu8FAmr82i8bFIAAAAAABAAO
bWFudTIsMi41KzEuMTIsMCwzAAoJEG5Y3pAfABrvviIQAJb76i3JbXRkghATCsTB
c4wHymqar2T5jb7TJz7fBIIyQtQJPRVIMmhrq2OBLfX05OzzgsLJ8LyJpGgrRL9/
k5LPg8r7SC/L95KhUnN+je54SgzUAbXonXiJOlDvTXwaohrbfaCoqbK9RT9o9Eb4
tIsrmDJqMptbMEXWssm6+uSt45g+N7DC6ueaf70PgkUBnjHgj2aJWRchplj/Z7x2
vs3DVoNdwChdCgKkUbAivOZcAd+G3yChgpuFGrnfO2epAa8/KBalUMkQwQ0e3T87
X0izoosWBFc5R4puWaK05k2HbGAc8pELTWwiuVhNODbmIl3POYTZTHntwATofP0r
P7Is1K9wuCLllxDZ9fzY0tOd4qTYh+ROt9Q/y7NinMMX48rTkpGWoRnqRk79Zdlo
balg9pqZ8WN7wxnq7Yi/GftCP5xWRaeQnhmr1bcNpDhebYHlqysCo0vsgabcPxIQ
bCrhwU2DhW+JZ+KqZgoPJgV+HphtB6vt7D13+UDL3Abza4yJXcs2633zftF9DAyP
r45G7AM/4QKFF2bbJpYOfpMgE8rJr1tDlnyufdeinH6sM/v+G7D8d2WRXX4InRNX
tMWngMyRt3H3g4uDsbsVDqGVeQY1Yw2mQ2FAvpquIuIveXb53HUPndzmLFowlaVj
uLPLObDYhIJ/zVyW6ybGrp87
=q2qt
-----END PGP SIGNATURE-----