CVE-2026-23764: VB-Audio Voicemeeter & Matrix Drivers DoS via Corrupted IoAllocateMdl Length
VB-Audio Voicemeeter, Voicemeeter Banana, and Voicemeeter Potato (versions ending in 1.1.1.9, 2.1.1.9, and 3.1.1.9 and earlier, respectively), as well as VB-Audio Matrix and Matrix Coconut (versions ending in 1.0.2.2 and 2.0.2.2 and earlier, respectively), contain a vulnerability in their virtual audio drivers (vbvoicemeetervaio64*.sys, vbmatrixvaio64*.sys, vbaudio_vmauxvaio*.sys, vbaudio_vmvaio*.sys, and vbaudio_vmvaio3*.sys). The drivers allocate non-paged pool and map it into user space, where a length value associated with the allocation is exposed and can be modified by an unprivileged local attacker. On subsequent IOCTL handling, the corrupted length is used directly as the IoAllocateMdl length argument without adequate integrity checks before building and mapping the MDL, which can cause a kernel crash (BSoD), typically PAGE_FAULT_IN_NONPAGED_AREA. This flaw allows a local user to trigger a denial-of-service on affected Windows systems.
Security readout for executives and security teams
Plain-English summary
A local Windows user can crash systems running affected VB-Audio Voicemeeter or Matrix virtual audio drivers. This is not described as data theft or remote compromise, but it can disrupt workstations, studios, support environments, or shared machines where untrusted local users can log in.
Executive priority
Treat this as a moderate availability risk, not a breach-class issue. Patch exposed workstations during the next maintenance window, sooner for shared systems where a local user could intentionally crash production audio or support operations.
Technical view
The drivers expose a length value in user-mapped memory. A low-privileged local attacker can corrupt that value, and later IOCTL handling uses it as the IoAllocateMdl length without adequate integrity checks, causing kernel crashes such as PAGE_FAULT_IN_NONPAGED_AREA. CVSS 4.0 score is 6.8, availability impact high.
Likely exposure
Exposure is limited to Windows systems with affected VB-Audio Voicemeeter Standard, Banana, Potato, Matrix, or Matrix Coconut driver versions installed. Highest concern is shared desktops, lab machines, streaming or audio-production workstations, and environments where non-admin local users have access.
Exploitation context
The CVE is not listed as KEV, and the source bundle does not show active exploitation. A public technical write-up is tagged as exploit material, so defenders should assume reproducibility may be possible while avoiding claims of in-the-wild use.
Researcher notes
Key issue is CWE-823: use of an out-of-range or corrupted length in kernel MDL allocation flow. The advisory describes local, low-complexity, low-privilege denial of service with no stated confidentiality or integrity impact. Affected version metadata in the bundle is sparse, so rely on the narrative version ranges and vendor notes.
Mitigation direction
Inventory installed VB-Audio Voicemeeter and Matrix products on Windows endpoints.
Upgrade to vendor releases newer than the affected version endings.
Remove unused VB-Audio virtual audio drivers from systems that do not need them.
Review VB-Audio release notes and advisories before fleet-wide remediation.
Prioritize shared or kiosk-like Windows systems with local user access.
Validation and detection
Check installed product versions against the affected version endings in the CVE description.
Look for affected driver filenames such as vbvoicemeetervaio64*.sys and vbmatrixvaio64*.sys.
Review crash telemetry for PAGE_FAULT_IN_NONPAGED_AREA on systems using these drivers.
Confirm updated drivers are loaded after installation or remediation.
Document any systems requiring deferred update due to audio workflow dependencies.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-823: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-823 · source CWE mapping
Use of Out-of-range Pointer Offset
Use of Out-of-range Pointer Offset represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.