ALSA: mpu401: Check card index validity at probe (CVE-2026-80969) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-80969

ALSA: mpu401: Check card index validity at probe

Answer in brief

CVE-2026-80969 records a Unknown severity vulnerability in ALSA: mpu401: Check card index validity at probe. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 11, 2026Updated Sep 11, 2026Source checked Sep 11, 2026First seen by HOL Sep 11, 2026Material review Sep 11, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <76b6bc38d0f310c0ae1b2a2ebabe2947d92c601a \|\| >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cc4215cc2a4b2a9cf8b1952bbe8d5bf925acb3ea \|\| >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8adda66edf795d4648f8e26f312e4414c535d25a \|\| >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f7dcecb92ed192ff5fcf842918fb1aaea84b5bdd \|\| >=0 <6.12.109 \|\| >=0 <6.18.50 \|\| >=0 <7.2.4	76b6bc38d0f310c0ae1b2a2ebabe2947d92c601a, cc4215cc2a4b2a9cf8b1952bbe8d5bf925acb3ea, 8adda66edf795d4648f8e26f312e4414c535d25a, f7dcecb92ed192ff5fcf842918fb1aaea84b5bdd, 6.12.109, 6.18.50, 7.2.4

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux.
Review the reported fix. Update Linux/Linux to 76b6bc38d0f310c0ae1b2a2ebabe2947d92c601a if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 11, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: ALSA: mpu401: Check card index validity at probe mpu401 driver blindly trusts that the given devptr->id value is within the proper card index range at probe. 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.

Quoted source text, attributed separately from HOL analysis.