CVE-2026-74504: ALSA: seq: Fix division by zero in initialize_timer()
In the Linux kernel, the following vulnerability has been resolved:
ALSA: seq: Fix division by zero in initializetimer()
A userspace-driven ALSA timer (SNDUTIMER) lets an unprivileged user set the backing sndtimer's hardware resolution to an arbitrary 64-bit value via SNDRVTIMERIOCTLCREATE. sndutimercreate() only rejects zero.
When such a timer is bound to a sequencer queue, initializetimer() computes the tick period as
tmr->ticks = 1000000000 / (r freq);
where r is that user-controlled resolution and freq is the sequencer update rate in Hz, clamped to MINFREQUENCY..MAXFREQUENCY (10..6250). A resolution of 2^63 makes the 64-bit product r freq wrap to zero for any even freq, including DEFAULTFREQUENCY (1000), so the division faults with a divide-by-zero.
The division runs under tmr->lock with interrupts disabled, so the oops leaves the spinlock held and hangs the CPU. It is reachable by an unprivileged user with access to /dev/snd/timer and /dev/snd/seq.
Oops: divide error: 0000 [#1] SMP KASAN PTI CPU: 7 UID: 1000 PID: 456 Comm: alsasequtimer Not tainted 7.2.0-rc4+ RIP: 0010:initializetimer.constprop.0+0x20a/0x2d0 sndseqtimerstart+0x15e/0x2b0 sndseqcontrolqueue+0x56f/0xba0 sndseqwrite+0x3e0/0x730
Reject an overflowing product with checkmuloverflow() and fall back to a single tick, which also avoids feeding a wrapped-but-nonzero divisor (e.g. 2^63 1000 mod 2^64 == 0, or other resolutions wrapping to a small value) into the period computation.
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.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 - Compensating control
In initialize_timer(), use check_mul_overflow() when computing r * freq and fall back to a single tick if the product overflows.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-74504?
The severity of CVE-2026-74504 is rated as medium with a risk score of 45.
What systems are affected by CVE-2026-74504?
CVE-2026-74504 affects the Linux kernel specifically related to the ALSA timer functionality.
How do I fix CVE-2026-74504?
To fix CVE-2026-74504, it is recommended to update to the latest patched version of the Linux kernel.
What does CVE-2026-74504 exploit?
CVE-2026-74504 exploits a division by zero vulnerability in the ALSA seq functionality of the Linux kernel.
Is CVE-2026-74504 a privilege escalation vulnerability?
Yes, CVE-2026-74504 allows an unprivileged user to manipulate the snd_timer's hardware resolution.