CVE-2026-23762: VB-Audio Voicemeeter & Matrix Drivers DoS via MmMapLockedPagesSpecifyCache
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 map non-paged pool memory into user space via MmMapLockedPagesSpecifyCache using UserMode access without proper exception handling. If the mapping fails, such as when a process has exhausted available virtual address space, MmMapLockedPagesSpecifyCache raises an exception that is not caught, causing a kernel crash (BSoD), typically SYSTEM_SERVICE_EXCEPTION with STATUS_NO_MEMORY. This flaw allows a local unprivileged user to trigger a denial-of-service on affected Windows systems.
Security readout for executives and security teams
Plain-English summary
A local, unprivileged Windows user can crash systems running affected VB-Audio virtual audio drivers. The impact is denial of service: blue screen, interrupted audio workflows, and possible loss of unsaved work. The provided sources do not indicate data theft, privilege escalation, or remote compromise.
Executive priority
Treat as a moderate availability risk. Patch during the next endpoint maintenance cycle, faster for production audio systems or shared machines where local users could disrupt operations.
Technical view
Affected VB-Audio drivers call MmMapLockedPagesSpecifyCache with UserMode access to map non-paged pool memory into user space. When mapping fails, the raised exception is not handled, causing a kernel crash, typically SYSTEM_SERVICE_EXCEPTION with STATUS_NO_MEMORY.
Likely exposure
Exposure is limited to Windows systems with affected Voicemeeter Standard, Banana, Potato, Matrix, or Matrix Coconut virtual audio drivers installed. The issue is local-only, but shared workstations, studios, kiosks, or systems with multiple local users are more exposed.
Exploitation context
The CVE is not marked KEV, and the bundle provides no active exploitation evidence. A cited public research repository is tagged as exploit-related, so defenders should assume local crash reproduction details may be publicly available.
Researcher notes
This is CWE-755: improper handling of exceptional conditions in kernel driver memory mapping. Validation should focus on version and driver presence, not live crash testing on production systems.
Mitigation direction
Upgrade to vendor-fixed VB-Audio releases where applicable.
Prioritize shared or business-critical audio workstations.
Remove unused VB-Audio virtual audio drivers from managed endpoints.
Restrict local interactive access on affected systems.
Monitor vendor guidance for exact fixed versions and upgrade notes.
Validation and detection
Inventory installed VB-Audio products and driver versions.
Check for affected driver filenames on Windows endpoints.
Confirm versions are newer than the affected release thresholds.
Review crash logs for SYSTEM_SERVICE_EXCEPTION or STATUS_NO_MEMORY.
Validate remediation by confirming updated driver versions.
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-755: 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-755 · source CWE mapping
Improper Handling of Exceptional Conditions
Improper Handling of Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.