CVE-2026-90220

ALSA: seq: Don't leak the extension cell pointer in the bounce payload

N/A
Published: September 17, 2026 at 04:07 PM UTC
Updated: October 21, 2026 at 01:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: Don't leak the extension cell pointer in the bounce payload The bounce_error_event() embeds the failed event in the bounce payload by pointing data.ext.ptr at it. When that event is a queued variable-length event, its own data.ext.ptr holds the address of its first extension cell, put there by snd_seq_event_dup(). The payload goes out verbatim through snd_seq_expand_var_event(), so the address reaches userspace. That is the same address commit 705dd6dcbc0e ("ALSA: seq: Clear variable event pointer on read") removed from the event header. The read path still clears it there, just above the call that expands the payload. Embed a sanitised copy instead, treated exactly as snd_seq_read() treats the header. A stack copy is enough because delivery is synchronous and snd_seq_event_dup() copies before returning. An unprivileged client reaches this by setting SNDRV_SEQ_FILTER_BOUNCE, queueing a variable-length event to a port that does not exist and reading the bounce back. Eight bytes on 64-bit, from its own pool.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

0527a56cb327021cb73167cfddf0e49efa043500527a56cb327021cb73167cfddf0e49efa435006.12.976.18.406.6.1607.1.57.293d260ce43a81df579c98bee92b91316df9c1c57dae23c545eb5a2be3b27a82fd0f611894fb8ab69eae296065ede41a24040e6a7c909ec970f78b4ebefc86691e4d8083d9e380ea95042c2cf679f65fd
Vendor states this is fixed in 42c3f856d13a91a0d4c302a0c6854813621136db (fixed)
Vendor states this is fixed in 59e1592d3c270ff4642d5d6dc55c545306eb0693 (fixed)
Vendor states this is fixed in 6e6e471eef1d5d8cb056c7d364023fe048249204 (fixed)
Vendor states this is fixed in b1e8d40663997aacaa198f37ce6893e07aaba77a (fixed)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card