Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-45258: Out-of-bounds kernel memory access in FreeBSD sound(4) /dev/dsp mmap handling

Published Jun 27, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS0.15%4th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Freebsd
IdentifiersCVE-2026-45258CWE-190 · Integer Overflow or Wraparound

CVE-2026-45258 is a local kernel memory corruption and disclosure vulnerability in FreeBSD's sound(4) mmap path, specifically in dsp_mmap_single(). The function validated a user-requested mapping by checking the sum of a user-controlled offset and length against the backing audio buffer size. Because this addition could overflow, a sufficiently large offset and length could wrap around and incorrectly satisfy the bounds check. The offset was then narrowed from 64 bits to 32 bits during conversion to a buffer address, producing a mapping that extended beyond the intended audio buffer into unrelated kernel memory. As a result, a local user able to access /dev/dsp could obtain an mmap region referencing kernel memory outside the audio buffer.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an unprivileged local user on a system with an audio device to read and write unrelated kernel memory through the /dev/dsp mmap interface. This can be used for local privilege escalation, potentially resulting in full system compromise or root-level control. At minimum, the flaw can destabilize or crash the kernel, causing denial of service.

Mitigation

If you can’t patch tonight, do this now.

No workaround is available according to the advisory. Systems without sound devices are unaffected.

Remediation

Patch, then assume compromise.

Apply the FreeBSD security updates that address the sound(4) mmap vulnerabilities. The provided context states fixes were released in FreeBSD 15.1-RELEASE-p1, 15.0-RELEASE-p11, 14.4-RELEASE-p7, and 14.3-RELEASE-p16. FreeBSD recommends upgrading to a supported corrected release or security branch and rebooting. Where applicable, use freebsd-update, pkg upgrade for eligible base-package installations, or apply the vendor patch for the affected release, then rebuild the kernel and reboot.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FreebsdFreebsdoperating_system
FAQ

Frequently asked questions

Is CVE-2026-45258 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-45258 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-45258?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-45258, the earliest disclosed Jun 10, 2026.
Is there a patch for CVE-2026-45258?
Apply the FreeBSD security updates that address the sound(4) mmap vulnerabilities. The provided context states fixes were released in FreeBSD 15.1-RELEASE-p1, 15.0-RELEASE-p11, 14.4-RELEASE-p7, and 14.3-RELEASE-p16.
What products are affected by CVE-2026-45258?
Freebsd.
How severe is CVE-2026-45258?
CVE-2026-45258 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.15% (4th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.