What’s Vulnerable › Vulnerabilities
CVE-2026-23761: VB-Audio Voicemeeter & Matrix Drivers DoS via Improper FILE_OBJECT FsContext Initialization
- Severity: medium (CVSS 6.9 v4.0)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.2% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-01-22 · updated 2026-06-17
- Weakness: CWE-824
Description
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.
Affected products
- VB-Audio Software Matrix: through 1.0.2.2
- VB-Audio Software Matrix Coconut: through 2.0.2.2
- VB-Audio Software Voicemeeter Banana: through 2.1.1.9
- VB-Audio Software Voicemeeter Potato: through 3.1.1.9
- VB-Audio Software Voicemeeter (Standard): through 1.1.1.9
References
- https://forum.vb-audio.com/viewtopic.php?p=7527#p7527
- https://forum.vb-audio.com/viewtopic.php?p=7574#p7574
- https://github.com/emkaix/security-research/tree/main/CVE-2026-23761
- https://vb-audio.com/
- https://www.vulncheck.com/advisories/vb-audio-voicemeeter-and-matrix-drivers-dos-via-improper-file-object-fscontext-initialization
Get alerted when CVE-2026-23761 or the next vulnerability affects your stack