Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
Linux Kernel: UAC3 Header Validation Error in USB Audio
published 7 months ago
Summary
A security issue was fixed in the Linux kernel. It affects the way the system checks USB audio devices. A malicious device could have caused the system to read data from the wrong place, potentially leading to a security problem. If you use Linux, make sure your system is up to date to prevent this issue.
What to do
- Update linux kernel to version 6.19.7.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| Linux | linux | kernel |
>= 6.19.0, < 6.19.7 Fix: upgrade to 6.19.7
|
Original advisory text
ALSA: usb-audio: Use correct version for UAC3 header validation
In the Linux kernel, the following vulnerability has been resolved:
ALSA: usb-audio: Use correct version for UAC3 header validation
The entry of the validators table for UAC3 AC header descriptor is
defined with the wrong protocol version UAC_VERSION_2, while it should
have been UAC_VERSION_3. This results in the validator never matching
for actual UAC3 devices (protocol == UAC_VERSION_3), causing their
header descriptors to bypass validation entirely. A malicious USB
device presenting a truncated UAC3 header could exploit this to cause
out-of-bounds reads when the driver later accesses unvalidated
descriptor fields.
The bug was introduced in the same commit as the recently fixed UAC3
feature unit sub-type typo, and appears to be from the same copy-paste
error when the UAC3 section was created from the UAC2 section.
ALSA: usb-audio: Use correct version for UAC3 header validation
The entry of the validators table for UAC3 AC header descriptor is
defined with the wrong protocol version UAC_VERSION_2, while it should
have been UAC_VERSION_3. This results in the validator never matching
for actual UAC3 devices (protocol == UAC_VERSION_3), causing their
header descriptors to bypass validation entirely. A malicious USB
device presenting a truncated UAC3 header could exploit this to cause
out-of-bounds reads when the driver later accesses unvalidated
descriptor fields.
The bug was introduced in the same commit as the recently fixed UAC3
feature unit sub-type typo, and appears to be from the same copy-paste
error when the UAC3 section was created from the UAC2 section.
References
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git Product
- https://git.kernel.org/stable/c/0dcd1ed96c03459cf14706885c9dd3c1fd8bd29f URL
- https://git.kernel.org/stable/c/1e5753ff4c2e86aa88516f97a224c90a3d0b133e URL
- https://git.kernel.org/stable/c/499ffd15b00dc91ac95c28f76959dfb5cdcc84d5 URL
- https://git.kernel.org/stable/c/54f9d645a5453d0bfece0c465d34aaf072ea99fa URL
- https://git.kernel.org/stable/c/a0c6ae2ea84528f198bf7fd0117f12fd0cf6d7cc URL
- https://git.kernel.org/stable/c/d3904ca40515272681ae61ad6f561c24f190957f URL
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23318... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-23318 Vendor Advisory
Timeline
Published25 Mar 2026
Updated2 May 2026
First seen2 May 2026
Track software like this
Free during beta