CVE-2026-74503: ALSA: timer: Clear SNDRV_TIMER_IFLG_DEAD once the close completes
In the Linux kernel, the following vulnerability has been resolved:
ALSA: timer: Clear SNDRVTIMERIFLGDEAD once the close completes
sndtimercloselocked() marks an instance with SNDRVTIMERIFLGDEAD and returns early when the flag is already set, but the flag is never cleared again. A completed close ends in removeslavelinks(), which leaves timeri->timer NULL, so a second close is already harmless through the timer == NULL path; the early return can only be reached by an instance that was opened again in between. For such an instance the close unlinks nothing, so sndtimerinstancefree() frees an object that is still on timer->openlisthead, still on sndtimermasterlist if it was opened with a slave key, still owns any adopted slaves, and still holds its timer and module references.
sndseqtimeropen() reopens an instance exactly like that: it retries its fallback open on the same object after a failure that has already run sndtimercloselocked() internally. An unprivileged user with access to /dev/snd/timer and /dev/snd/seq can force that failure, since sndtimercheckmaster() returns -EBUSY when a pending slave matches the new master's (slaveclass, slaveid) key and the target timer has reached maxinstances, and SNDRVTIMERIOCTLSELECT with devclass = SNDRVTIMERCLASSSLAVE keeps the caller-supplied devsclass, so a sequencer queue's key can be forged. The freed instance is afterwards dereferenced by any further sndtimeropen() on that timer, by sndtimercheckslave(), and by /proc/asound/timers, which faults on the stale ti->owner pointer.
The flag only has to be visible while the close is in progress, which is all its other users need. Clear it in removeslavelinks(), under the same timer->lock that sets it, once the instance is off every list.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.103 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.44 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.1 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.1.8 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 6.12.107-1Fixed in 6.12.117-1Fixed in 7.3.4-1Fixed in 7.3.5-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.117-1~deb12u1 - Upgrade
Upgrade
ubuntu/linux-aws-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.18~24.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1020.21~24.04.2 - Upgrade
Upgrade
ubuntu/linux-azure-fde-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1019.19~24.04.1 - Upgrade
Upgrade
ubuntu/linux-gcp-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.19~24.04.1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-oracle-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1016.18~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 7.0.0-1020.21 - Upgrade
Upgrade
ubuntu/linux-azure-fdeto a version that resolves this vulnerability.Fixed in 7.0.0-1019.19 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-gketo a version that resolves this vulnerability.Fixed in 7.0.0-1010.11 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-raspito a version that resolves this vulnerability.Fixed in 7.0.0-1023.23 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 7.0.0-43.43.1 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1 - Configuration
In remove_slave_links(), clear SNDRV_TIMER_IFLG_DEAD under timer->lock once the instance is off every list.
Linux kernel ALSA timer SNDRV_TIMER_IFLG_DEAD = cleared
Event History
Frequently Asked Questions
What is the severity of CVE-2026-74503?
The severity of CVE-2026-74503 is rated as 72.
How do I fix CVE-2026-74503?
To fix CVE-2026-74503, update your Linux kernel to the latest version that includes the patch for this vulnerability.
What component is affected by CVE-2026-74503?
CVE-2026-74503 affects the ALSA timer component in the Linux kernel.
What happens when CVE-2026-74503 is exploited?
Exploitation of CVE-2026-74503 could lead to improper handling of timer instances, potentially causing unexpected behavior.
When was CVE-2026-74503 published?
CVE-2026-74503 was published on August 15, 2026.