# CVE-2026-45258: Multiple vulnerabilities in the sound(4) mmap path

> Integer overflow in FreeBSD sound driver allows local users to read/write kernel memory, leading to privilege escalation or system crash.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jun 2026
- **Updated:** 30 Jun 2026

## What is CVE-2026-45258?

CVE-2026-45258 is a high-severity vulnerability in Freebsd Freebsd, published on 27 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

dsp_mmap_single() validated the requested mapping by checking the sum of the user-supplied offset and length against the buffer size.  This addition could overflow, so that a large offset and length wrapped around and passed the check.  The offset was then narrowed from 64 to 32 bits when converted to a buffer address, yielding a mapping that extended past the audio buffer into unrelated kernel memory.

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).

Weakness: CWE-787 (Out-of-bounds Write), CWE-681 (Incorrect Conversion between Numeric Types), CWE-190 (Integer Overflow or Wraparound), CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-45258?

It affects 1 product.


Products: Freebsd Freebsd.

## How do I fix CVE-2026-45258?

No fix has been published for CVE-2026-45258 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-45258 being exploited?

There is no known exploitation of CVE-2026-45258 in the wild and no public exploit code.

Public exploit code:

- 1-day exploit for CVE-2026-45258 (github_poc): https://github.com/Yayoi-cs/CVE-2026-45258_1day_LPE_exploit

## Other vulnerabilities in Freebsd Freebsd

- [CVE-2018-17160](https://insights.sbomify.com/CVE-2018-17160/): Memory corruption in FreeBSD (critical 10.0)
- [CVE-2014-3954](https://insights.sbomify.com/CVE-2014-3954/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-4304](https://insights.sbomify.com/CVE-2006-4304/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-0226](https://insights.sbomify.com/CVE-2006-0226/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0002](https://insights.sbomify.com/CVE-2004-0002/): Denial of service in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45258 and fix it if it is affected.

What it is: CVE-2026-45258 is a high-severity vulnerability in Freebsd Freebsd, published on 27 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-45258 in the wild and no public exploit code.

Affected product: Freebsd Freebsd. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45258/ (Markdown: https://insights.sbomify.com/CVE-2026-45258/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45258
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45258
- OSV: https://osv.dev/vulnerability/CVE-2026-45258

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45258/
Summaries are generated and may contain mistakes; the official description above is the record.