CVE-2026-99314
ALSA: us122l: Add missing NULL check in usb_stream_hwdep_mmap()
What happened?
In the Linux kernel, the following vulnerability has been resolved:
ALSA: us122l: Add missing NULL check in usb_stream_hwdep_mmap()
usb_stream_hwdep_mmap() reads us122l->sk.s and dereferences it without checking for NULL. The stream object is released by usb_stream_free(), which is reached through us122l_stop() both when the device is disconnected and when us122l_start() fails, and it leaves us122l->sk.s set to NULL. The hwdep file stays usable after that, so a later mmap()
KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017] RIP: 0010:usb_stream_hwdep_mmap+0x107/0x890 sound/usb/usx2y/us122l.c:182
crashes while reading s->read_size, which sits at offset 0x10.
That NULL is an expected state for this field: usb_stream_hwdep_vm_fault(), usb_stream_hwdep_poll(), usb_stream_hwdep_ioctl(), usb_stream_stop() and usb_stream_free() all test it before use. Only the mmap callback misses the check, so let it return -ENODEV, matching what the other hwdep mapping in usx2yhwdeppcm.c does when its shared buffer has not been allocated.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: 030a07e441296c372f946cd4065b5d831d8dc40c to < 0f128b326d3defab6bf5c33c09e55addd87e74ec; affected: 030a07e441296c372f946cd4065b5d831d8dc40c to < 03d3690ba06713358cd8c89bbec090040c272438; affected: 030a07e441296c372f946cd4065b5d831d8dc40c to < 6fdd96fa2f7a70d61eeed166e520a990c40ff223; affected: 030a07e441296c372f946cd4065b5d831d8dc40c to < f5d3eb483fed59fc0f3b059b8b6a32cedc922360 | See vendor advisory |
| LinuxLinux | affected: 2.6.28; unaffected: 0 to < 2.6.28; unaffected: 6.12.118 to ≤ 6.12.*; unaffected: 6.18.64 to ≤ 6.18.*; unaffected: 7.3.5 to ≤ 7.3.*; unaffected: 7.4-rc2 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99314
- https://git.kernel.org/stable/c/0f128b326d3defab6bf5c33c09e55addd87e74ec
- https://git.kernel.org/stable/c/03d3690ba06713358cd8c89bbec090040c272438
- https://git.kernel.org/stable/c/6fdd96fa2f7a70d61eeed166e520a990c40ff223
- https://git.kernel.org/stable/c/f5d3eb483fed59fc0f3b059b8b6a32cedc922360