Home / mailings FreeBSD Security Advisory FreeBSD-SA-26:88.sound
Posted on 18 November 2026
FreeBSD security notificat=============================================================================FreeBSD-SA-26:88.sound Security Advisory
The FreeBSD Project
Topic: Privilege escalation via sound software buffer resizing
Category: core
Module: sound
Announced: 2026-11-17
Credits: OpenAI Security Research Team
Affects: All supported versions of FreeBSD.
Corrected: 2026-11-17 17:06:08 UTC (stable/15, 15.2-STABLE)
2026-11-17 17:08:26 UTC (releng/15.1, 15.1-RELEASE-p7)
2026-11-17 17:02:55 UTC (stable/14, 14.5-STABLE)
2026-11-17 17:05:18 UTC (releng/14.5, 14.5-RELEASE-p4)
2026-11-17 17:04:20 UTC (releng/14.4, 14.4-RELEASE-p13)
CVE Name: CVE-2026-127741
For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit <URL:https://security.FreeBSD.org/>.
I. Background
FreeBSD provides audio support through the sound(4) driver, which
presents each audio device as a set of character device nodes such as
/dev/dsp. Each audio channel has a software buffer, which applications
can resize using ioctl(2).
II. Problem Description
When reading from or writing to an audio channel, the sound(4) driver
dropped the channel lock while copying data between the channel's
software buffer and userspace. The buffer resize path did not account
for this, so a concurrent resize could free the buffer while the copy was
in progress.
III. Impact
An unprivileged local user with access to a /dev/dsp* sound device can
exploit this race to trigger a use-after-free in the kernel and escalate
privileges.
IV. Workaround
No workaround is available. Systems with no sound devices 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:88/sound.patch
# fetch https://security.FreeBSD.org/patches/SA-26:88/sound.patch.asc
# gpg --verify sound.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
<URL:https://www.FreeBSD.org/handbook/kernelconfig.html> 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/ f3afd16367c5 stable/15-n286879
releng/15.1/ 2c29a955d314 releng/15.1-n283683
stable/14/ 2a5981445627 stable/14-n275584
releng/14.5/ da654629ecd0 releng/14.5-n274919
releng/14.4/ fe39499d2178 releng/14.4-n273820
- -------------------------------------------------------------------------
Run the following command to see which files were modified by a
particular commit:
# git show --stat <commit hash>
Or visit the following URL, replacing NNNNNN with the hash:
<URL:https://cgit.freebsd.org/src/commit/?id=NNNNNN>
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
<URL:https://www.cve.org/CVERecord?id=CVE-2026-127741>
The latest revision of this advisory is available at
<URL:https://security.FreeBSD.org/advisories/FreeBSD-SA-26:88.sound.asc>
