CVE-2026-98742: ALSA: seq: Serialize compat port-info ioctls
ALSA: seq: Serialize compat port-info ioctls
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.113-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.10-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.113-1~deb12u1 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.10.273 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.15.224 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.191 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.160 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.113 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.56 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.2.10 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1
Event History
Frequently Asked Questions
What conditions are required to trigger this issue?
The issue requires concurrent compat-mode translated port-info ioctl requests, specifically concurrent CREATE_PORT requests against the ALSA sequencer client. The race occurs because the compat path reaches the port handlers without holding client->ioctl_mutex.
What can happen if the race succeeds?
Multiple requests can pass the port-count check before insertion is serialized, allowing a computed port index to exceed the address field range and wrap to an existing index. During later subscriber teardown, the duplicate address can resolve to the wrong port and access a freed subscriber.
What is the available mitigation if an update cannot be applied immediately?
The supplied information identifies serialization with client->ioctl_mutex as the fix, matching the native ioctl path. It does not provide a configuration workaround or other temporary mitigation.