CVE-2026-23763: VB-Audio Matrix Drivers Local Privilege Escalation via Kernel Memory Exposure
VB-Audio Matrix and Matrix Coconut (versions ending in 1.0.2.2 and 2.0.2.2 and earlier, respectively), contain a local privilege escalation vulnerability in the VBMatrix VAIO virtual audio driver (vbmatrixvaio64*_win10.sys). The driver allocates a 128-byte non-paged pool buffer and, upon receiving IOCTL 0x222060, maps it into user space using an MDL and MmMapLockedPagesSpecifyCache. Because the allocation size is not page-aligned, the mapping exposes the entire 0x1000-byte kernel page containing the buffer plus adjacent non-paged pool allocations with read/write permissions. An unprivileged local attacker can open a device handle (using the required 0x800 attribute flag), invoke the IOCTL to obtain the mapping, and then read or modify live kernel objects and pointers present on that page. This enables bypass of KASLR, arbitrary kernel memory read/write within the exposed page, corruption of kernel objects, and escalation to SYSTEM.
Security readout for executives and security teams
Plain-English summary
This is a local Windows privilege-escalation flaw in VB-Audio Matrix drivers. A user already on a machine could abuse the driver to expose writable kernel memory and potentially become SYSTEM. It is high priority for endpoints where Matrix or Matrix Coconut is installed; no active exploitation is stated in the provided sources.
Executive priority
Treat as high priority where the software is installed. This is not remotely exploitable by itself, but it can turn a normal local account or foothold into SYSTEM on affected Windows endpoints.
Technical view
The VBMatrix VAIO driver maps a small non-page-aligned non-paged-pool allocation into user space for a driver IOCTL. The resulting page mapping can expose adjacent kernel pool data with read/write permissions. The CVE describes KASLR bypass, kernel object corruption, and escalation to SYSTEM from a low-privileged local context.
Likely exposure
Exposure is likely limited to Windows systems with VB-Audio Matrix or Matrix Coconut installed, including the vulnerable VBMatrix VAIO driver. The bundle identifies Matrix versions ending in 1.0.2.2 and Matrix Coconut versions ending in 2.0.2.2 and earlier as affected.
Exploitation context
The provided sources describe a local attack requiring low privileges and no user interaction. They include a technical exploit-tagged reference, but KEV is false and the bundle does not state active exploitation in the wild.
Researcher notes
The key issue is improper exposure of kernel memory through a user-mode mapping of a non-page-aligned kernel allocation. Evidence supports local privilege escalation impact, but the bundle does not provide safe fixed-version detail beyond vendor patch references.
Mitigation direction
Inventory endpoints for VB-Audio Matrix and Matrix Coconut installations.
Check installed driver versions against vendor release notes and the CVE record.
Apply VB-Audio patched releases or vendor-recommended updates where applicable.
Restrict local interactive access on affected workstations until remediated.
Monitor vendor guidance for exact fixed-version and removal instructions.
Validation and detection
Confirm whether vbmatrixvaio64*_win10.sys is present on Windows endpoints.
Record installed Matrix and Matrix Coconut application and driver versions.
Verify updated systems no longer run affected driver builds.
Review EDR telemetry for unusual local privilege-escalation attempts involving this driver.
Track remediation status separately for creative, audio, and workstation fleets.
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-668: 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.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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.
1CVSS vectors
3Timeline events
1ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
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-668 · source CWE mapping
Exposure of Resource to Wrong Sphere
Exposure of Resource to Wrong Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.