CVE-2026-80968: ALSA: mts64: Check card index validity at probe
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.
Affected Software
Event History
Frequently Asked Questions
What conditions are required to trigger the issue?
The mts64 driver must be bound through sysfs with a device card ID that is negative, such as a value used to represent "none." The vulnerable path occurs during driver probe, before the card index is used to access index[] and related parameters.
Who is most likely exposed?
Systems using the Linux kernel mts64 ALSA driver are relevant. Exposure specifically depends on the driver being bound through sysfs with an invalid negative card index; the provided information does not establish that normal default driver binding supplies such a value.
What should be done if the fix cannot be applied immediately?
Avoid binding the mts64 driver through sysfs with a negative card ID. Validate that any configured or supplied card index is within the valid range before triggering driver probe.
How can administrators identify potentially affected configurations?
Review sysfs-based mts64 driver binding and any associated card ID values. A configuration that supplies a negative ID, including a value intended to mean "none," is potentially affected.