ALSA: caiaq: fix out-of-bounds read in the Traktor Kontrol S4 input parser
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.18% (FIRST EPSS).
- Fixed version: Linux Linux 05df59b9a61f7ca66548df079d306c41da23845d, 0680413f2f10aab43878dd3db711a6a9e45bab7c, 3cad86197c7bf8b45bb1d8adc1099d0913e80469; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1.
Low priority for now. Upgrade to Linux Linux 05df59b9a61f7ca66548df079d306c41da23845d, 0680413f2f10aab43878dd3db711a6a9e45bab7c, 3cad86197c7bf8b45bb1d8adc1099d0913e80469; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-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: fix out-of-bounds read in the Traktor Kontrol S4 input parser snd_usb_caiaq_tks4_dispatch() decodes the Traktor Kontrol S4 input stream in fixed 16-byte (TKS4_MSGBLOCK_SIZE) message blocks. On every iteration it advances buf and subtracts the block size while looping on "while (len)". len is urb->actual_length. That value is supplied by the device and is not guaranteed to be a multiple of 16. When a final short block leaves len between 1 and 15, the loop runs once more, reads up to buf[15], and then does "len -= TKS4_MSGBLOCK_SIZE". As len is unsigned this underflows to a huge value. The loop then keeps iterating and walking buf far past the end of the 512-byte ep4_in_buf, reading out of bounds until a bogus block id happens to be hit. Iterate only while a full message block is available. This stops the unsigned underflow and silently drops any trailing partial block, which carries no complete control value anyway. The sibling endpoint-4 parsers are not affected. The Traktor Kontrol X1 and Maschine arms in snd_usb_caiaq_ep4_reply_dispatch() floor urb->actual_length before dispatching.
- Published
- Jul 25, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.1% · 7th 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.1%
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
- 2.6.37affected
- 15c5ab607045e278ebf4d2ca4aea2250617d50ca and later · before de5f9edc705497b1b2c6b173b22f283486d2fd91affected · git
- 15c5ab607045e278ebf4d2ca4aea2250617d50ca and later · before 70d6d4cfa4ad09688aed2ec8a0cfa72c31f60334affected · git
- 15c5ab607045e278ebf4d2ca4aea2250617d50ca and later · before 884f575cc6acb136eb4a161d925147f85b59c27eaffected · git
- 15c5ab607045e278ebf4d2ca4aea2250617d50ca and later · before 05df59b9a61f7ca66548df079d306c41da23845daffected · git
- 15c5ab607045e278ebf4d2ca4aea2250617d50ca and later · before 3cad86197c7bf8b45bb1d8adc1099d0913e80469affected · git
- 15c5ab607045e278ebf4d2ca4aea2250617d50ca and later · before a5fd3122283bf75c04f6414bf610100beb0565b0affected · git
- 15c5ab607045e278ebf4d2ca4aea2250617d50ca and later · before 0680413f2f10aab43878dd3db711a6a9e45bab7caffected · git
- 15c5ab607045e278ebf4d2ca4aea2250617d50ca and later · before f7f3f9fd81e7adbaa12c2e62ee07f0e094a543fdaffected · git
- before 2.6.37not affected · 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 | before 6.1.180-1 | 6.1.180-1 |
| Debian:12 | linux-6.12 | before 6.12.100-1~deb12u1 | 6.12.100-1~deb12u1 |
| Debian:13 | linux | before 6.12.96-1 | 6.12.96-1 |
| Debian:14 | linux | before 7.1.4-1 | 7.1.4-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-64484Jul 25, 2026 · ALSA: es1938: check snd_ctl_new1() return value0Monitor
- ← EarlierCVE-2026-64486Jul 25, 2026 · ALSA: cmipci: check snd_ctl_new1() return value0Monitor
- Later →CVE-2026-64488Jul 25, 2026 · ALSA: aoa: check snd_ctl_new1() return value0Monitor
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 | 05df59b9a61f7ca66548df079d306c41da23845d | Vendor (CNA) |
| Linux Linux | 0680413f2f10aab43878dd3db711a6a9e45bab7c | Vendor (CNA) |
| Linux Linux | 3cad86197c7bf8b45bb1d8adc1099d0913e80469 | Vendor (CNA) |
| Linux Linux | 70d6d4cfa4ad09688aed2ec8a0cfa72c31f60334 | Vendor (CNA) |
| Linux Linux | 884f575cc6acb136eb4a161d925147f85b59c27e | Vendor (CNA) |
| Linux Linux | a5fd3122283bf75c04f6414bf610100beb0565b0 | Vendor (CNA) |
| Linux Linux | de5f9edc705497b1b2c6b173b22f283486d2fd91 | Vendor (CNA) |
| Linux Linux | f7f3f9fd81e7adbaa12c2e62ee07f0e094a543fd | Vendor (CNA) |
| azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 | 6.6.145.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.100-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.
No dated events beyond publication.
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/0680413f2f10aab43878dd3db711a6a9e45bab7c
- git.kernel.org/stable/c/3cad86197c7bf8b45bb1d8adc1099d0913e80469
- git.kernel.org/stable/c/70d6d4cfa4ad09688aed2ec8a0cfa72c31f60334
- git.kernel.org/stable/c/884f575cc6acb136eb4a161d925147f85b59c27e
- git.kernel.org/stable/c/a5fd3122283bf75c04f6414bf610100beb0565b0
- git.kernel.org/stable/c/de5f9edc705497b1b2c6b173b22f283486d2fd91
- git.kernel.org/stable/c/f7f3f9fd81e7adbaa12c2e62ee07f0e094a543fd
Vendor advisories and official records. Exploit/PoC links are deliberately left out.