CVE-2026-23761: VB-Audio Voicemeeter & Matrix Drivers DoS via Improper FILE_OBJECT FsContext Initialization
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). When a handle is opened with a special file attribute value, the drivers improperly initialize FILE_OBJECT->FsContext to a non-pointer magic value. If subsequent operations are not handled by the VB-Audio driver and are forwarded down the audio driver stack (e.g., via PortCls to ks.sys), the invalid FsContext value can be dereferenced, causing a kernel crash (BSoD), typically SYSTEM_SERVICE_EXCEPTION with STATUS_ACCESS_VIOLATION. 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
This vulnerability lets any local user crash a Windows system running affected VB-Audio virtual audio drivers. It is a denial-of-service issue, not evidence of data theft or remote takeover. Business urgency depends on where these audio tools are installed, especially shared workstations, production streaming systems, labs, or kiosks.
Executive priority
Treat this as a targeted availability risk. It does not currently warrant emergency enterprise-wide response unless affected drivers are on critical or shared Windows systems, but it should be remediated during normal vulnerability cycles.
Technical view
Affected VB-Audio drivers can set FILE_OBJECT->FsContext to an invalid non-pointer value when opened with a special file attribute. Later operations forwarded down the audio stack may dereference it in kernel context, causing a BSoD such as SYSTEM_SERVICE_EXCEPTION with STATUS_ACCESS_VIOLATION.
Likely exposure
Exposure is limited to Windows systems with affected Voicemeeter, Voicemeeter Banana, Voicemeeter Potato, Matrix, or Matrix Coconut versions and their listed virtual audio drivers installed.
Exploitation context
The CVE source says exploitation is local, low complexity, unauthenticated, and requires no user interaction. KEV is false, and the provided bundle does not cite active exploitation in the wild.
Researcher notes
Evidence points to CWE-824 improper initialization in kernel driver FILE_OBJECT state. Public technical material exists, including an exploit-tagged reference, so validation should remain defensive and avoid reproducing crash paths on production systems.
Mitigation direction
Inventory endpoints for the affected VB-Audio products and listed driver filenames.
Check VB-Audio release notes and update affected installations per vendor guidance.
Remove affected VB-Audio products from systems where they are not required.
Prioritize shared, kiosk, studio, and production endpoints where local users can cause outages.
Validation and detection
Compare installed versions against the affected version thresholds in the CVE description.
Confirm whether listed VB-Audio driver files are present on Windows endpoints.
Review crash telemetry for SYSTEM_SERVICE_EXCEPTION or STATUS_ACCESS_VIOLATION involving the listed drivers.
Verify updated or removed endpoints no longer report affected product 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-824: 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-824 · source CWE mapping
Access of Uninitialized Pointer
Access of Uninitialized Pointer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.