CVE-2026-124019 in VB-CABLEinfo

Summary

by MITRE • 11/16/2026

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 to write attacker-controlled values sequentially into kernel memory corrupting kernel globals and object pointers, or read past an array boundary to leak kernel memory, resulting in local privilege escalation or denial of service via a kernel bug check.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 11/16/2026

The vulnerability resides within the VB-CABLE virtual audio device kernel streaming driver, specifically identified as vbaudio_cable64_win10.sys version 10.0.10011.16384. This component is responsible for handling audio stream properties in Windows operating systems through the Kernel Streaming (KS) architecture. The core technical flaw involves improper input validation within three specific property handlers associated with the KSPROPSETID_Audio set: MUTE, VOLUMELEVEL, and PEAKMETER2. These handlers are designed to process requests from user-mode applications seeking to control audio device parameters. However, they fail to adequately verify the bounds of array indices or loop terminators when processing specific sentinel values intended to represent all channels simultaneously.

When a local standard user submits an all-channels sentinel value through these property interfaces, the driver incorrectly interprets this value as either a direct array index or a loop termination condition without performing necessary range checks. This logic error allows for out-of-bounds memory access operations. In the case of write vulnerabilities, the attacker can supply controlled values that are sequentially written into kernel memory locations outside the intended buffer boundaries. These writes target critical kernel globals and object pointers, effectively corrupting the state of the operating system's core structures. For read vulnerabilities, the flaw permits reading data from beyond the allocated array limits, leading to information leakage of sensitive kernel memory contents.

The operational impact of this vulnerability is severe due to its potential for local privilege escalation. By exploiting the out-of-bounds write capability, an attacker can overwrite function pointers or security-critical structures within the kernel space. This manipulation allows the execution of arbitrary code with SYSTEM-level privileges, bypassing standard user account restrictions. Alternatively, if the exploitation focuses on memory corruption that destabilizes critical system components, it results in a denial of service condition manifested as a kernel bug check, commonly known as a Blue Screen of Death (BSOD), which crashes the entire operating system and disrupts availability for all users.

This vulnerability is categorized under CWE-125, Out-of-bounds Read, and CWE-787, Out-of-bounds Write, reflecting the fundamental memory safety failures in the driver's input handling logic. From a tactical perspective, it aligns with MITRE ATT&CK technique T1068, Exploitation for Privilege Escalation, as well as T1531, Account Access Removal, if used to crash systems or disable security services. The attack vector is classified as Local (T1059), requiring physical or logical access to the machine with a standard user account, leveraging the accessible low-integrity KS filter device object to initiate the malicious property requests.

Mitigation strategies should prioritize immediate patching of the VB-CABLE driver to versions that implement strict bounds checking for all channel indices and sentinel values. System administrators must ensure that virtual audio drivers are updated regularly through official vendor channels. In environments where such devices are not strictly necessary, disabling or uninstalling the VB-CABLE service can reduce the attack surface by removing the vulnerable kernel module from memory entirely. Additionally, enforcing application control policies to restrict unsigned or untrusted driver loading can provide an additional layer of defense against exploitation attempts targeting similar vulnerabilities in other third-party drivers.

Responsible

VulnCheck

Reservation

11/06/2026

Disclosure

11/16/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you need the next level of professionalism?

Upgrade your account now!