CVE-2026-90220: ALSA: seq: Don't leak the extension cell pointer in the bounce payload
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 42c3f856d13a91a0d4c302a0c6854813621136db, 59e1592d3c270ff4642d5d6dc55c545306eb0693, 6.12.110.
Low priority for now. Upgrade to Linux Linux 42c3f856d13a91a0d4c302a0c6854813621136db, 59e1592d3c270ff4642d5d6dc55c545306eb0693, 6.12.110 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 17, 2026
- Updated
- Oct 21, 2026
- EPSS
- 0.2% · 9th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- eae296065ede41a24040e6a7c909ec970f78b4eb, 0527a56cb327021cb73167cfddf0e49efa043500, 7.2affected
- 93d260ce43a81df579c98bee92b91316df9c1c57 and later · before 42c3f856d13a91a0d4c302a0c6854813621136dbaffected · git
- dae23c545eb5a2be3b27a82fd0f611894fb8ab69 and later · before b1e8d40663997aacaa198f37ce6893e07aaba77aaffected · git
- efc86691e4d8083d9e380ea95042c2cf679f65fd and later · before 6e6e471eef1d5d8cb056c7d364023fe048249204affected · git
- efc86691e4d8083d9e380ea95042c2cf679f65fd and later · before 59e1592d3c270ff4642d5d6dc55c545306eb0693affected · git
- 6.12.97 and later · before 6.12.110affected · semver
- 6.18.40 and later · before 6.18.52affected · semver
- 6.6.160 and later · before 6.7affected · semver
- 7.1.5 and later · before 7.2affected · semver
- before 7.2not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90218Sep 17, 2026 · RDMA/cma: Fix WARNING in res_to_rt0Monitor
- ← EarlierCVE-2026-90219Sep 17, 2026 · RDMA/cxgb4: Free debugfs on registration failure0Monitor
- Later →CVE-2026-90221Sep 17, 2026 · nfc: nci: fix use of uninitialized memory in CORE_INIT_RSP parsing0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 42c3f856d13a91a0d4c302a0c6854813621136db | Vendor (CNA) |
| Linux Linux | 59e1592d3c270ff4642d5d6dc55c545306eb0693 | Vendor (CNA) |
| Linux Linux | 6.12.110 | Vendor (CNA) |
| Linux Linux | 6.18.52 | Vendor (CNA) |
| Linux Linux | 6.7 | Vendor (CNA) |
| Linux Linux | 6e6e471eef1d5d8cb056c7d364023fe048249204 | Vendor (CNA) |
| Linux Linux | 7.2 | Vendor (CNA) |
| Linux Linux | b1e8d40663997aacaa198f37ce6893e07aaba77a | Vendor (CNA) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.