CVE-2026-49417: FreeBSD Audio Use-After-Free Privilege Escalation (CWE-416)
A use-after-free vulnerability in FreeBSD's audio device handling allows unprivileged local users to read and write kernel memory. When an audio device is closed, its backing buffer may be freed while memory mappings remain valid, leaving the process able to access the freed region. Since audio device nodes are world-accessible by default, any local user with access to the system can exploit this to either escalate privileges to gain full system control or crash the kernel, causing a denial of service.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.0 HIGH · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weaknesses (CWE)
- CWE-416
- Affected products
- 31 configuration(s)
- Published / Modified
- 2026-06-27 / 2026-07-01
NVD description (verbatim)
Second, the audio buffer backing a mapping could be freed when the device was closed even though the mapping remained valid. The freed memory could then be reused elsewhere while still accessible through the stale mapping. The /dev/dsp device nodes are world-accessible by default. On a system with an audio device, either issue allows an unprivileged local user to read and write kernel memory, which can be used to escalate privileges, potentially gaining full control of the affected system. At a minimum, an attacker can crash the kernel, resulting in a Denial of Service (DoS).
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-49417 is a use-after-free vulnerability (CWE-416) affecting FreeBSD's audio subsystem. The flaw occurs in the /dev/dsp device driver when a device is closed: the audio buffer backing a memory mapping is freed, but the mapping itself remains valid in user-space. This creates a window where user-space code can still access the deallocated kernel memory through the stale mapping. An attacker can then cause that freed memory to be reallocated and reused by other kernel subsystems, enabling arbitrary kernel memory read and write primitives. The CVSS v3.1 score of 7.0 (HIGH) reflects high impact on confidentiality, integrity, and availability, though exploitation requires local access and moderately complex conditions.
Business impact
On affected FreeBSD systems running audio hardware, this vulnerability enables local privilege escalation without authentication. A low-privileged user (or an attacker gaining initial shell access) can leverage kernel memory corruption to achieve root-level control, potentially compromising the entire system. For organizations running FreeBSD on servers, desktops, or embedded systems with audio capabilities, compromise could lead to data theft, malware installation, lateral movement, or loss of system availability. The practical impact depends on the system's role: critical infrastructure, database servers, or sensitive workstations face elevated risk.
Affected systems
FreeBSD systems equipped with audio devices are affected. The vulnerability requires the /dev/dsp device node to be present and accessible, which is the default configuration on FreeBSD installations with audio hardware. Both modern and legacy audio subsystems in FreeBSD are impacted. Systems without audio hardware or with audio device nodes explicitly restricted are not vulnerable, though this is uncommon in typical deployments.
Exploitability
Exploitation requires local access to the affected FreeBSD system and low privileges (standard user account). No network access is needed. The CVSS vector reflects AC:H (moderately complex), indicating that triggering the precise race condition or timing window may require experimentation or knowledge of system state. However, the barrier to attempting exploitation is low: any local user can open /dev/dsp and attempt to craft malicious audio mappings. Once successful, the attacker gains kernel-level read and write capabilities. This vulnerability is not currently tracked in the CISA Known Exploited Vulnerabilities (KEV) catalog, though active public exploitation has not been widely reported as of the publication date.
Remediation
The primary remediation is to apply FreeBSD security updates that patch the audio buffer handling logic. Patches address the use-after-free by ensuring that memory mappings are properly invalidated or the backing buffer is not freed while mappings remain active. Temporary mitigations include restricting access to /dev/dsp via file permissions (e.g., chmod 600 or removal of world-readable access) or disabling audio drivers if not required. However, permission-based mitigations are not a full substitute for patching, as they depend on correct deployment and maintenance.
Patch guidance
Contact FreeBSD security advisories and your distribution's patch channels for the specific patched version. Verify patch application by confirming the audio driver code no longer exhibits the buffer-freeing behavior described in this advisory. Organizations should prioritize patching systems with network exposure or those running sensitive services, while extending the timeline for isolated development or test systems as risk tolerance allows. Test patches in a non-production environment first to ensure stability with your audio configuration.
Detection guidance
Monitor system logs and kernel debugging output for use-after-free warnings or crashes in the audio subsystem, typically appearing as kernel panics or kmesg entries mentioning dsp, audio, or memory corruption. Intrusion detection systems can monitor for suspicious /dev/dsp access patterns or rapid open/close cycles. Host-based monitoring for privilege escalation attempts (e.g., failed execve of setuid binaries followed by successful root shell access) may reveal active exploitation. However, detection of successful exploitation in real-time is difficult; kernel crash dumps or memory forensics are more reliable post-incident indicators.
Why prioritize this
This vulnerability merits immediate attention for FreeBSD-based systems in production. The combination of high CVSS score (7.0), kernel-level impact, local privilege escalation capability, and default world-accessible attack surface makes it a priority target for attackers with system access. While not yet in the KEV catalog, the simplicity of the attack vector and the severity of impact justify rapid patching. Organizations should treat this as a critical issue for internet-facing systems and medium-to-high priority for internal infrastructure.
Risk score, explained
The CVSS v3.1 score of 7.0 (HIGH) reflects: (1) High confidentiality impact—kernel memory is readable; (2) High integrity impact—kernel memory is writable, enabling privilege escalation; (3) High availability impact—DoS is trivial via kernel crash; (4) Local attack vector—attacker must have shell access; (5) Low privileges required—any user can attack; (6) Moderately high complexity—the race condition or precise conditions may require some effort to trigger reliably. The score appropriately weights the severe but locally-scoped nature of the threat.
Frequently asked questions
Do I need audio hardware to be vulnerable?
Yes. The vulnerability requires an audio device to be present and /dev/dsp to exist. Systems without audio hardware or with audio drivers explicitly disabled are not affected. However, most production FreeBSD systems with standard hardware configurations do have audio support enabled by default.
Can this be exploited remotely?
No. This is a strictly local vulnerability requiring shell access or the ability to execute code on the target system. It cannot be exploited over the network directly, but it is a powerful tool for an attacker who has already gained initial local access to escalate to root.
What is the difference between this and a simple privilege escalation bug?
This vulnerability allows arbitrary kernel memory read and write, which is far more powerful than a simple privilege escalation flaw. An attacker can inspect kernel data structures, disable security features, inject code into the kernel, or craft elaborate exploits. Simple privilege escalation bugs are typically narrower in scope.
Will restricting /dev/dsp permissions prevent exploitation?
Restricting permissions to /dev/dsp (e.g., removing world-readable access) will prevent unprivileged users from opening the device. However, this is not a complete fix because users with group access or other privilege levels may still be affected, and this mitigation can break legitimate audio applications. Always pair permission changes with patching when possible.
This analysis is provided for informational and educational purposes to assist security decision-making. It is not a substitute for official vendor advisories, security bulletins, or professional security consultation. Patch versions, supported product versions, and specific remediation steps must be verified against official FreeBSD security advisories and your organization's vendor documentation. Testing all patches in non-production environments before deployment is strongly recommended. The timing and severity of this vulnerability may vary depending on your system configuration, deployment model, and threat model. SEC.co and its contributors assume no liability for damages resulting from the application or misapplication of this information. Source: NVD (public-domain), retrieved 2026-08-05. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-49412HIGHFreeBSD IPv6 Multicast Filter Use-After-Free Privilege Escalation
- CVE-2025-60464HIGHGPAC MP4Box Use-After-Free DoS Vulnerability
- CVE-2025-60467HIGHGPAC MP4Box Use-After-Free DoS Vulnerability
- CVE-2026-0125HIGHAndroid VPU Race Condition Local Privilege Escalation
- CVE-2026-0137HIGHAndroid Edge TPU Use-After-Free Privilege Escalation
- CVE-2026-0143HIGHAndroid LWIS Use-After-Free Privilege Escalation (CVSS 7.8 HIGH)
- CVE-2026-10000HIGHChrome Sandbox Escape via Use-After-Free in Password Handling
- CVE-2026-10001HIGHChrome Sandbox Escape via PerformanceManager Use-After-Free