CVE-2026-68202

published 10 Aug 2026 · updated 17 Nov 2026

ALSA: seq: close a re-opened queue timer in the destructor

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 fb40d03ed792a8a8bf77aa0ee15df57b0ff78b07, Kernel 24f0cabf173539f048946c8fc221131dc221f277, Kernel 2c4dc0ed50b05cd847a4b34b8cebf0775f19aeb9 and 12 more.

In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: close a re-opened queue timer in the destructor queue_delete() closes the queue timer, then frees it. snd_seq_timer_close() clears q->timer->timeri. snd_use_lock_sync() then drains borrowers, and snd_seq_timer_delete() frees q->timer. A borrower can re-open the timer inside that window. A SET_QUEUE_CLIENT that took a queueptr() use_lock reference before the queue was unlinked runs snd_seq_timer_open() after the close. Open refuses re-open only while timeri is set, and the close just cleared it, so it re-opens timeri. snd_seq_timer_delete() does not close that instance. Its snd_seq_timer_stop() is a no-op, because running was cleared first. So it frees q->timer with the instance still live. The queue is freed next. The instance stays on the global timer with callback_data pointing at the freed queue. A non-owner START on the unlocked queue arms it. The next tick derefs the freed queue in snd_seq_timer_interrupt(). Reachable by an unprivileged user with access to /dev/snd/seq. No CAP and no queue ownership required. Close any lingering instance in the destructor. There, ->timeri can no longer change: the queue is unlinked and all use_lock borrowers have drained, so no snd_seq_queue_use() can re-open it. Close it before clearing q->timer. snd_timer_close() waits for any in-flight snd_seq_timer_interrupt() to finish, and that callback still reads q->timer (via snd_seq_check_queue()), so q->timer must stay valid until it drains.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fb40d03ed792a8a8bf77aa0ee15df57b0ff78b07, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <24f0cabf173539f048946c8fc221131dc221f277, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2c4dc0ed50b05cd847a4b34b8cebf0775f19aeb9, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <31a6163e301d832060f8236f1ed17cbc1ca198df, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6a10025c7fd09a7d2af37a3ae1da188569fce470, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7478ef94b49bc9789cf1a003deec58b42283dde4, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9d9be6fc30f384f92c4e1b8ed40bd9d4796b7833, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b7feeaca1f53b10df9b4de9eaf611767ca70dc92, =2.6.12fb40d03ed792a8a8bf77aa0ee15df57b0ff78b07, 24f0cabf173539f048946c8fc221131dc221f277, 2c4dc0ed50b05cd847a4b34b8cebf0775f19aeb9, 31a6163e301d832060f8236f1ed17cbc1ca198df, 6a10025c7fd09a7d2af37a3ae1da188569fce470, 7478ef94b49bc9789cf1a003deec58b42283dde4, 9d9be6fc30f384f92c4e1b8ed40bd9d4796b7833, b7feeaca1f53b10df9b4de9eaf611767ca70dc92
linux-kernel: Kernel>=5.11.0 <5.15.217, >=5.16.0 <6.1.183, >=6.13.0 <6.18.42, >=6.19.0 <7.1.6, >=6.2.0 <6.6.148, >=6.7.0 <6.12.101, >=2.6.12 <5.10.2665.15.217, 6.1.183, 6.18.42, 7.1.6, 6.6.148, 6.12.101, 5.10.266

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-68202 severity on Zeptric[![CVE-2026-68202](https://zeptric.io/badge/cve/CVE-2026-68202.svg)](https://zeptric.io/cve/CVE-2026-68202)