CVE-2026-68200

published 10 Aug 2026 · updated 28 Oct 2026

ALSA: timer: don't re-enter an instance callback that is still running

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel c1078130a4cd7e738f4b73afe99b3e68cbfbf884, Kernel 1395327a96614885552bae5fbb650e6dd182d49b, Kernel 70d28bfcd6224eed75986b3b987b997e59643fa4 and 4 more.

In the Linux kernel, the following vulnerability has been resolved: ALSA: timer: don't re-enter an instance callback that is still running The userspace-driven timer (utimer) TRIGGER ioctl calls snd_timer_interrupt() directly with no serialization, so two threads triggering the same utimer can run snd_timer_interrupt() on one snd_timer concurrently. snd_timer_process_callbacks() drops timer->lock around each instance callback and marks the in-flight callback with the single SNDRV_TIMER_IFLG_CALLBACK bit; snd_timer_close_locked() waits on that bit to drain an in-flight callback before freeing the instance. The bit cannot represent two concurrent callbacks: when a second interrupt re-queues an instance whose callback is still running, both run at once, the first to finish clears the bit, and the close-path drain then frees the instance (and its callback_data) while the other callback is still live - a use-after-free reachable by any user able to open /dev/snd/timer, both via a user timer instance and via a sequencer queue timer bound to the utimer. snd_timer_interrupt() sets IFLG_CALLBACK before dropping timer->lock, so a concurrent interrupt already observes it under the lock. Skip re-queuing an instance (and its slaves) to the ack/sack list while its callback is in flight; the accumulated pticks are delivered on the next tick, so no event is lost.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=37745918e0e7575bc40f38da93a99b9fa6406224 <c1078130a4cd7e738f4b73afe99b3e68cbfbf884, >=37745918e0e7575bc40f38da93a99b9fa6406224 <1395327a96614885552bae5fbb650e6dd182d49b, >=37745918e0e7575bc40f38da93a99b9fa6406224 <70d28bfcd6224eed75986b3b987b997e59643fa4, >=37745918e0e7575bc40f38da93a99b9fa6406224 <996c24377eea4d4506b7c3ccbbf1e490440b5e0b, =6.12c1078130a4cd7e738f4b73afe99b3e68cbfbf884, 1395327a96614885552bae5fbb650e6dd182d49b, 70d28bfcd6224eed75986b3b987b997e59643fa4, 996c24377eea4d4506b7c3ccbbf1e490440b5e0b
linux-kernel: Kernel>=6.13.0 <6.18.42, >=6.19.0 <7.1.6, >=6.12.0 <6.12.1016.18.42, 7.1.6, 6.12.101

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-68200 severity on Zeptric[![CVE-2026-68200](https://zeptric.io/badge/cve/CVE-2026-68200.svg)](https://zeptric.io/cve/CVE-2026-68200)