ALSA: mts64: Check card index validity at probe
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 036e7aa793375ab16ea0f64b8de6673220416cc1, 1566ca99fc0e892b9164ad893d268b00064fff54, 5168a6241e953ecadb0ec05609649f6a7367fef8.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 036e7aa793375ab16ea0f64b8de6673220416cc1, 1566ca99fc0e892b9164ad893d268b00064fff54, 5168a6241e953ecadb0ec05609649f6a7367fef8 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
In the Linux kernel, the following vulnerability has been resolved: ALSA: mts64: Check card index validity at probe Although mts64 driver has a check of the given devptr->id value, it doesn't check for a negative id, which is often given as "none" or such value when bound via sysfs. This may lead to OOB access for index[] and other parameters. Add a sanity check for the card index and warn/correct it if it's a value out of the range.
- Published
- Sep 11, 2026
- Updated
- Sep 14, 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
- 2.6.19affected
- 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad and later · before 1566ca99fc0e892b9164ad893d268b00064fff54affected · git
- 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad and later · before 5d986d8c9e616636032636d99133f2535f94300daffected · git
- 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad and later · before 5168a6241e953ecadb0ec05609649f6a7367fef8affected · git
- 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad and later · before 9cd7c59a106e7267d0cbcf68670594584d8689d0affected · git
- 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad and later · before 036e7aa793375ab16ea0f64b8de6673220416cc1affected · git
- 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad and later · before a4e774eeb61aec64da5b03d3becffde26f7fe4deaffected · git
- 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad and later · before cf3af453a48c8d905512dfc44a5a59439b70f4f0affected · git
- 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad and later · before d18a260720f86a5f8b5fcfefc4ba2e9dd01c10f8affected · git
- before 2.6.19not 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 | all versions | — |
| 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
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
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 | 036e7aa793375ab16ea0f64b8de6673220416cc1 | Vendor (CNA) |
| Linux Linux | 1566ca99fc0e892b9164ad893d268b00064fff54 | Vendor (CNA) |
| Linux Linux | 5168a6241e953ecadb0ec05609649f6a7367fef8 | Vendor (CNA) |
| Linux Linux | 5d986d8c9e616636032636d99133f2535f94300d | Vendor (CNA) |
| Linux Linux | 9cd7c59a106e7267d0cbcf68670594584d8689d0 | Vendor (CNA) |
| Linux Linux | a4e774eeb61aec64da5b03d3becffde26f7fe4de | Vendor (CNA) |
| Linux Linux | cf3af453a48c8d905512dfc44a5a59439b70f4f0 | Vendor (CNA) |
| Linux Linux | d18a260720f86a5f8b5fcfefc4ba2e9dd01c10f8 | Vendor (CNA) |
| 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-1085 · Sep 14, 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/1566ca99fc0e892b9164ad893d268b00064fff54
- git.kernel.org/stable/c/5168a6241e953ecadb0ec05609649f6a7367fef8
- git.kernel.org/stable/c/5d986d8c9e616636032636d99133f2535f94300d
- git.kernel.org/stable/c/9cd7c59a106e7267d0cbcf68670594584d8689d0
- git.kernel.org/stable/c/a4e774eeb61aec64da5b03d3becffde26f7fe4de
- git.kernel.org/stable/c/cf3af453a48c8d905512dfc44a5a59439b70f4f0
- git.kernel.org/stable/c/d18a260720f86a5f8b5fcfefc4ba2e9dd01c10f8
Vendor advisories and official records. Exploit/PoC links are deliberately left out.