CVE-2026-31620: ALSA: usx2y: us144mkii: fix NULL deref on missing interface 0
Noroxi assessment
Priority: Monitor (action score 18/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.19% (FIRST EPSS).
- Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 09b145c1f1331c40dc955c0024d636f25417cddb, 48bd344e1040b9f2eb512be73c13f5db83efc191, d04dd67ab10dc978c6c843c6bd6a2a66a9444f51; azl3 kernel 6.6.130.1-3 on Azure Linux 3.0 6.6.134.1-2.
Low priority for now. Upgrade to Linux Linux 09b145c1f1331c40dc955c0024d636f25417cddb, 48bd344e1040b9f2eb512be73c13f5db83efc191, d04dd67ab10dc978c6c843c6bd6a2a66a9444f51; azl3 kernel 6.6.130.1-3 on Azure Linux 3.0 6.6.134.1-2 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: usx2y: us144mkii: fix NULL deref on missing interface 0 A malicious USB device with the TASCAM US-144MKII device id can have a configuration containing bInterfaceNumber=1 but no interface 0. USB configuration descriptors are not required to assign interface numbers sequentially, so usb_ifnum_to_if(dev, 0) returns will NULL, which will then be dereferenced directly. Fix this up by checking the return value properly.
- Published
- Apr 24, 2026
- Updated
- Nov 11, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- CWE-476
Report tools
Action score
18
Low priority for now.
- CVSS
- 18 / 40 · 4.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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.
Is your version affected? Check itNoroxi 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
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
- 6.18affected
- dee1bcf28a3dd13ddb2e9200407864f73e9c4d63 and later · before 09b145c1f1331c40dc955c0024d636f25417cddbaffected · git
- dee1bcf28a3dd13ddb2e9200407864f73e9c4d63 and later · before fbaf29ce00e7bce683f3faf4f2b326bd0a9e6602affected · git
- dee1bcf28a3dd13ddb2e9200407864f73e9c4d63 and later · before d04dd67ab10dc978c6c843c6bd6a2a66a9444f51affected · git
- dee1bcf28a3dd13ddb2e9200407864f73e9c4d63 and later · before 48bd344e1040b9f2eb512be73c13f5db83efc191affected · git
- before 6.18not affected · semver
- 6.18.24 and later · up to and including 6.18.*not affected · semver
- 6.19.14 and later · up to and including 6.19.*not affected · semver
- 7.0.1 and later · up to and including 7.0.*not affected · semver
- 7.1 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.18 and later · before 6.18.24
- linux linux kernel6.19 and later · before 6.19.14
- linux linux kernel7.0 and later · before 7.0.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:14 | linux | before 6.19.14-1 | 6.19.14-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-31618Apr 24, 2026 · fbdev: tdfxfb: avoid divide-by-zero on FBIOPUT_VSCREENINFO22Monitor
- ← EarlierCVE-2026-31619Apr 24, 2026 · ALSA: fireworks: bound device-supplied status before string array lookup22Monitor
- Later →CVE-2026-31621Apr 24, 2026 · bnge: return after auxiliary_device_uninit() in error path22Monitor
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 | 09b145c1f1331c40dc955c0024d636f25417cddb | Vendor (CNA) |
| Linux Linux | 48bd344e1040b9f2eb512be73c13f5db83efc191 | Vendor (CNA) |
| Linux Linux | d04dd67ab10dc978c6c843c6bd6a2a66a9444f51 | Vendor (CNA) |
| Linux Linux | fbaf29ce00e7bce683f3faf4f2b326bd0a9e6602 | Vendor (CNA) |
| azl3 kernel 6.6.130.1-3 on Azure Linux 3.0 | 6.6.134.1-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.19.14-1 · Debian:14 | 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
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 (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.