CVE-2026-68202

Received Received - Intake

Use-After-Free in Linux Kernel ALSA Sequencer

Publication date: 2026-08-10

Last updated on: 2026-10-19

Assigner: kernel.org

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-10

Last Modified

2026-10-19

Generated

2026-11-08

AI Q&A

2026-08-10

EPSS Evaluated

2026-11-07

NVD

CVE-2026-68202

EUVD

EUVD-2026-55303

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-416	The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Attack-Flow Graph

Executive Summary

This is a use-after-free vulnerability in the Linux kernel's ALSA sequencer subsystem. It occurs when a queue timer is closed and freed but later accessed through a stale pointer. An unprivileged user with access to /dev/snd/seq can trigger this by reopening a closed timer before it is fully destroyed, leading to a freed memory region being accessed by the timer interrupt handler.

Detection Guidance

This vulnerability is specific to the Linux kernel's ALSA sequencer subsystem and requires local access to /dev/snd/seq. Detection involves checking kernel logs for related errors or monitoring for unusual activity in the ALSA sequencer. No direct network detection commands are applicable.

Impact Analysis

This vulnerability could allow an attacker to cause a system crash or execute arbitrary code with kernel privileges. Since it is reachable by unprivileged users, it poses a significant security risk on affected Linux systems.

Compliance Impact

This vulnerability allows an unprivileged user to trigger a use-after-free condition in the Linux kernel's ALSA sequencer subsystem, potentially leading to arbitrary code execution. For compliance with standards like GDPR or HIPAA, which require robust security controls to protect sensitive data, this could indicate a failure to maintain system integrity and confidentiality. However, the provided CVE details do not explicitly link this issue to compliance impacts.

Mitigation Strategies

Update the Linux kernel to the latest stable version that includes the fix for this vulnerability. If immediate patching is not possible, restrict access to /dev/snd/seq by adjusting permissions or using mandatory access controls to limit exposure.

Hi! I’m here to help you understand CVE-2026-68202. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70

EPSS Chart

Security Radar

News mentioning this vulnerability

Loading related security news...