CVE-2026-90033: ALSA: usb-audio: fix OOB write in snd_usbmidi_us122l_output()
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.20% (FIRST EPSS).
- Fixed version: Linux Linux 1d4add2b832b56f81bb0eab065ec35c610343018, 2dae0e3a59e31f78222279d544b98e747cd1fbff, 5538daf2a5cc80ac3f3e913c0db045d92d995d40; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1d4add2b832b56f81bb0eab065ec35c610343018, 2dae0e3a59e31f78222279d544b98e747cd1fbff, 5538daf2a5cc80ac3f3e913c0db045d92d995d40; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.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: usb-audio: fix OOB write in snd_usbmidi_us122l_output() The snd_usbmidi_us122l_output() picks a count of 2 on anything slower than high speed and never relates it to ep->max_transfer. The URB buffer holds exactly max_transfer bytes, so a device declaring a one byte bulk endpoint takes two bytes from snd_rawmidi_transmit(), and the memset that pads the rest computes 1 - 2 in int and wraps to SIZE_MAX. Only 0x800e and 0x800f are pinned to nine bytes. The US-122MKII at 0x0644:0x8021 falls to the default and takes usb_maxpacket(), which the USB core only clamps downward. The akai and novation output ops in this file were given the same guard recently. Do the same here.
- Published
- Sep 16, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 10th 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
- 2.6.28affected
- 030a07e441296c372f946cd4065b5d831d8dc40c and later · before 5538daf2a5cc80ac3f3e913c0db045d92d995d40affected · git
- 030a07e441296c372f946cd4065b5d831d8dc40c and later · before a441a8e52148c91c2f2a91f42e3b9bc961a13a4baffected · git
- 030a07e441296c372f946cd4065b5d831d8dc40c and later · before 2dae0e3a59e31f78222279d544b98e747cd1fbffaffected · git
- 030a07e441296c372f946cd4065b5d831d8dc40c and later · before 1d4add2b832b56f81bb0eab065ec35c610343018affected · git
- 030a07e441296c372f946cd4065b5d831d8dc40c and later · before de6d252f115be887a701c09a05cdb076f3a590c9affected · git
- 030a07e441296c372f946cd4065b5d831d8dc40c and later · before 9392a2c346762ffee8edd1ba8bac50d2e24a2ed7affected · git
- 030a07e441296c372f946cd4065b5d831d8dc40c and later · before 9d81885d97cba7796d1f8edc88f2499c8296f5b9affected · git
- 030a07e441296c372f946cd4065b5d831d8dc40c and later · before e4637ce34607f1733a34a57294966d26b263e626affected · git
- before 2.6.28not 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.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-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-90031Sep 16, 2026 · usb-storage: ene_ub6250: fix race between scan work and probe0Monitor
- ← EarlierCVE-2026-90032Sep 16, 2026 · media: usbtv: keep device alive while ALSA card exists31Monitor
- Later →CVE-2026-90034Sep 16, 2026 · usb: image: mdc800: change kmalloc() to kzalloc()0Monitor
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 | 1d4add2b832b56f81bb0eab065ec35c610343018 | Vendor (CNA) |
| Linux Linux | 2dae0e3a59e31f78222279d544b98e747cd1fbff | Vendor (CNA) |
| Linux Linux | 5538daf2a5cc80ac3f3e913c0db045d92d995d40 | Vendor (CNA) |
| Linux Linux | 9392a2c346762ffee8edd1ba8bac50d2e24a2ed7 | Vendor (CNA) |
| Linux Linux | 9d81885d97cba7796d1f8edc88f2499c8296f5b9 | Vendor (CNA) |
| Linux Linux | a441a8e52148c91c2f2a91f42e3b9bc961a13a4b | Vendor (CNA) |
| Linux Linux | de6d252f115be887a701c09a05cdb076f3a590c9 | Vendor (CNA) |
| Linux Linux | e4637ce34607f1733a34a57294966d26b263e626 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1114 · Sep 17, 2026(Linux Kernel Güvenlik Bildirimi)
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/2dae0e3a59e31f78222279d544b98e747cd1fbff
- git.kernel.org/stable/c/5538daf2a5cc80ac3f3e913c0db045d92d995d40
- git.kernel.org/stable/c/9392a2c346762ffee8edd1ba8bac50d2e24a2ed7
- git.kernel.org/stable/c/9d81885d97cba7796d1f8edc88f2499c8296f5b9
- git.kernel.org/stable/c/a441a8e52148c91c2f2a91f42e3b9bc961a13a4b
- git.kernel.org/stable/c/de6d252f115be887a701c09a05cdb076f3a590c9
- git.kernel.org/stable/c/e4637ce34607f1733a34a57294966d26b263e626
Vendor advisories and official records. Exploit/PoC links are deliberately left out.