CVE-2026-98837: ALSA: caiaq: unregister the input device when probe fails
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 0b7bd20f6379bc5e431fd74d866390f5b5b63f3c, 1d5d194594ff616ad36a052bde739d1cf5855b95, 2e5a413cc2a489c9427ecd3d73ad764bfb0c7103; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
Low priority for now. Upgrade to Linux Linux 0b7bd20f6379bc5e431fd74d866390f5b5b63f3c, 1d5d194594ff616ad36a052bde739d1cf5855b95, 2e5a413cc2a489c9427ecd3d73ad764bfb0c7103; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: ALSA: caiaq: unregister the input device when probe fails setup_card() registers the input device, whose name and phys point into struct snd_usb_caiaqdev, and then goes on to snd_card_register() and snd_usb_caiaq_control_init(). If either fails, snd_probe() calls snd_card_free(), which frees the device state but leaves the input device registered: card_free() only clears the pointer, and the input device is unregistered from snd_disconnect() alone. Reading its "uevent" attribute afterwards dereferences freed memory: BUG: KASAN: slab-use-after-free in string+0x4a9/0x4f0 Read of size 1 at addr ffff8880208f5043 by task caiaq/4967 add_uevent_var+0x183/0x3a0 input_dev_uevent+0x162/0x900 dev_uevent+0x2f1/0x870 uevent_show+0x1ca/0x3a0 ... Unregister the input device on the probe error path, as snd_disconnect() does. snd_usb_caiaq_input_disconnect() is a no-op when no input device was registered. Reproduced with a raw-gadget Audio Kontrol 1 and a temporary hack that makes snd_usb_caiaq_control_init() fail.
- Published
- Oct 18, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 096dd8519cf2f768e9e14f224b627f7aaee1a9c5, 7.1affected
- da938aa9fc7826901921dcea225948ab21a97e45 and later · before 7017c9dda1ebbab428a6fd29c841596b5c9c84d1affected · git
- 09616e25f502080ba684fc7fcf959d1376ab756d and later · before 8315ea07ebb2497531ff42dd640396f6f1d4a8f0affected · git
- b956e48371f2ff72b76be9a829800ecec963bd45 and later · before 1d5d194594ff616ad36a052bde739d1cf5855b95affected · git
- f537e3ad69609f6924a4db6b4a7f6561f5288bdd and later · before df2787819bd137111b56b8631dd581b0cce7144daffected · git
- 6251e3e256337a30160ef59ab1580dde4d1acd28 and later · before 850810c12686f80cdf7530f4f21e0157d904f739affected · git
- e59ecd4ee3a450db6cb4e4ecaa3efdd593f80056 and later · before 84727facd8506140cd04f2b0a8b1c4ddeac41ceaaffected · git
- 28abd224db4a49560b452115bca3672a20e45b2f and later · before 2e5a413cc2a489c9427ecd3d73ad764bfb0c7103affected · git
- 28abd224db4a49560b452115bca3672a20e45b2f and later · before 0b7bd20f6379bc5e431fd74d866390f5b5b63f3caffected · git
- 5.10.258 and later · before 5.10.273affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.10-1 | 7.2.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98835Oct 18, 2026 · iio: accel: kionix-kx022a: Fix array boundary check0Monitor
- ← EarlierCVE-2026-98836Oct 18, 2026 · ALSA: line6: reject oversized playback packets0Monitor
- Later →CVE-2026-98838Oct 18, 2026 · vt: skip screen update for DEC alignment test on backgroup consoles0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0b7bd20f6379bc5e431fd74d866390f5b5b63f3c | Vendor (CNA) |
| Linux Linux | 1d5d194594ff616ad36a052bde739d1cf5855b95 | Vendor (CNA) |
| Linux Linux | 2e5a413cc2a489c9427ecd3d73ad764bfb0c7103 | Vendor (CNA) |
| Linux Linux | 5.10.273 | Vendor (CNA) |
| Linux Linux | 5.15.224 | Vendor (CNA) |
| Linux Linux | 6.1.191 | Vendor (CNA) |
| Linux Linux | 6.12.113 | Vendor (CNA) |
| Linux Linux | 6.18.56 | Vendor (CNA) |
| Linux Linux | 6.6.160 | Vendor (CNA) |
| Linux Linux | 7.1 | Vendor (CNA) |
| Linux Linux | 7017c9dda1ebbab428a6fd29c841596b5c9c84d1 | Vendor (CNA) |
| Linux Linux | 8315ea07ebb2497531ff42dd640396f6f1d4a8f0 | Vendor (CNA) |
| Linux Linux | 84727facd8506140cd04f2b0a8b1c4ddeac41cea | Vendor (CNA) |
| Linux Linux | 850810c12686f80cdf7530f4f21e0157d904f739 | Vendor (CNA) |
| Linux Linux | df2787819bd137111b56b8631dd581b0cce7144d | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.159.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 7, 2026+20 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/1d5d194594ff616ad36a052bde739d1cf5855b95
- git.kernel.org/stable/c/2e5a413cc2a489c9427ecd3d73ad764bfb0c7103
- git.kernel.org/stable/c/7017c9dda1ebbab428a6fd29c841596b5c9c84d1
- git.kernel.org/stable/c/8315ea07ebb2497531ff42dd640396f6f1d4a8f0
- git.kernel.org/stable/c/84727facd8506140cd04f2b0a8b1c4ddeac41cea
- git.kernel.org/stable/c/850810c12686f80cdf7530f4f21e0157d904f739
- git.kernel.org/stable/c/df2787819bd137111b56b8631dd581b0cce7144d
Vendor advisories and official records. Exploit/PoC links are deliberately left out.