VB-Audio VB-CABLE Driver Out-of-Bounds Vulnerabilities
Is it fixed? Not yet.
Ongoing since Nov 16, 20:18 UTC. First reported Nov 16, 20:18 UTC.
What happened
VB-Audio VB-CABLE virtual audio device kernel streaming driver contains out-of-bounds read and write vulnerabilities in its KSPROPSETID_Audio MUTE, VOLUMELEVEL, and PEAKMETER2 property handlers. Local standard users can exploit these vulnerabilities due to improper bounds-checking of a sentinel value.
What caused it?
Improper bounds-checking of an all-channels sentinel value supplied by a local standard user, which is used as a loop terminator or array index.
Source: tenable.com
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Official fixTimeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on security advisory
VB-Audio VB-CABLE virtual audio device kernel streaming driver (vbaudio_cable64_win10.sys 10.0.10011.16384): CVE-2026-124019 (High)
Source
Evidence
1 report · 1 CVEShow
- [1]CVE First reportVB-Audio VB-CABLE virtual audio device kernel streaming driver (vbaudio_cable64_win10.sys 10.0.10011.16384): CVE-2026-124019 (High)(opens security advisory in a new tab)
High severity. VB-Audio VB-CABLE virtual audio device kernel streaming driver (vbaudio_cable64_win10.sys 10.0.10011.16384) contains out-of-bounds read and write vulnerabilities in its KSPROPSETID_Audio MUTE, VOLUMELEVEL, and PEAKMETER2 property handlers that allow a local standard user to supply an all-channels sentinel value which is improperly used as a loop terminator or array index instead of being bounds-checked. Attackers can exploit the accessible low-integrity KS filter device object…
by Tenable 0upvotes 0comments
FAQ
What happened in the Windows issue?
VB-Audio VB-CABLE virtual audio device kernel streaming driver contains out-of-bounds read and write vulnerabilities in its KSPROPSETID_Audio MUTE, VOLUMELEVEL, and PEAKMETER2 property handlers. Local standard users can exploit these vulnerabilities due to improper bounds-checking of a sentinel value.
What is affected by the Windows issue?
Windows (versions: vbaudio_cable64_win10.sys 10.0.10011.16384).
When did the Windows issue start and end?
It started Nov 16, 20:18 UTC and is still ongoing (2 d 8 h so far). This page updates as it develops.
How do I get alerts for Windows?
Subscribe to the Windows RSS feed for every new Windows incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Windows is down. Windows feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.