Skip to content
Noroxi
CVE-2026-80812· NVD / CVE Program· CNA Linux

ALSA: dummy: Check card index validity at probe

In the Linux kernel, the following vulnerability has been resolved: ALSA: dummy: Check card index validity at probe snd_dummy_probe() blindly trusts that the given devptr->id value is within the proper card index range. It's OK for the devices the driver itself creates at the module probe time, but if the device is bound manually via sysfs interface, this could be -1 as "none", and this leads 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.

—No exploit Fix available
Published
Sep 4, 2026
Updated
Sep 7, 2026
EPSS
0.2% · 11th percentile
CWE
—
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

—

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.16affected
    • 6e65c1cc4458b2784224759b6137a50d4f65e610 and later · before b7579e86afcec932e169d10e2d603abed8dd2fdfaffected · git
    • 6e65c1cc4458b2784224759b6137a50d4f65e610 and later · before 4d0892a90b57f0e89b274c3f3c51c2fa17937c88affected · git
    • 6e65c1cc4458b2784224759b6137a50d4f65e610 and later · before b20eb7ecbdaa3e649023fe41b177d90983ffb487affected · git
    • 6e65c1cc4458b2784224759b6137a50d4f65e610 and later · before c9f10a001c243d1f069ebb0e2f4999ad4043a254affected · git
    • 6e65c1cc4458b2784224759b6137a50d4f65e610 and later · before f20c2c32ec1c5c3526f29a03b487c55a5890996caffected · git
    • 6e65c1cc4458b2784224759b6137a50d4f65e610 and later · before 3dba0e92e18980cb5a4d70a9a263539ae4f0c7ecaffected · git
    • 6e65c1cc4458b2784224759b6137a50d4f65e610 and later · before 690b721b9595f9a43395fd4047a832c42b5b6078affected · git
    • 6e65c1cc4458b2784224759b6137a50d4f65e610 and later · before 02442d5fe8ee365a084b055d4fa81a0c1abfc3fdaffected · git
    • before 2.6.16not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.187-16.1.187-1
Debian:12linux-6.12before 6.12.107-1~deb12u16.12.107-1~deb12u1
Debian:13linuxbefore 6.12.107-16.12.107-1
Debian:14linuxbefore 7.1.12-17.1.12-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan
  • CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler
    40Plan
  • CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index
    40Plan
  • CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux02442d5fe8ee365a084b055d4fa81a0c1abfc3fdVendor (CNA)
Linux Linux3dba0e92e18980cb5a4d70a9a263539ae4f0c7ecVendor (CNA)
Linux Linux4d0892a90b57f0e89b274c3f3c51c2fa17937c88Vendor (CNA)
Linux Linux690b721b9595f9a43395fd4047a832c42b5b6078Vendor (CNA)
Linux Linuxb20eb7ecbdaa3e649023fe41b177d90983ffb487Vendor (CNA)
Linux Linuxb7579e86afcec932e169d10e2d603abed8dd2fdfVendor (CNA)
Linux Linuxc9f10a001c243d1f069ebb0e2f4999ad4043a254Vendor (CNA)
Linux Linuxf20c2c32ec1c5c3526f29a03b487c55a5890996cVendor (CNA)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.06.6.157.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.107-1~deb12u1 · Debian:12Package 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.

EPSS, last 120 days

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 researchers

Finders, 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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records