- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The Linux kernel's ALSA driver for the us122l USB audio device is missing a NULL check in its memory-mapping function, usb_stream_hwdep_mmap(). A memory-mapping call made after the device was disconnected or failed to start can dereference a NULL pointer and crash the kernel.
Original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch5/5No patch listed yet
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 47 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-99314 (ALSA: us122l: Add missing NULL check in usb_stream_hwdep_mmap()), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-99314 (entry last updated 2026-11-18):
Affected:
- Linux Linux: version range not reported
- Linux Linux: versions 2.6.28
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99314 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99314 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- 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
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-99314
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99314"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
2.6.28
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-99314 |
| Record | NVD · CVE-2026-99314 |
| Other links 4 | |
| Link | git.kernel.org · stable/c/0f128b326d3defab6bf5c33c09e55addd87e74ec |
| Link | git.kernel.org · stable/c/03d3690ba06713358cd8c89bbec090040c272438 |
| Link | git.kernel.org · stable/c/6fdd96fa2f7a70d61eeed166e520a990c40ff223 |
| Link | git.kernel.org · stable/c/f5d3eb483fed59fc0f3b059b8b6a32cedc922360 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-99314
Is CVE-2026-99314 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-99314?
Linux: version 2.6.28.Source: cve.now feed data