CVE-2026-46090 — ALSA: aloop: Fix peer runtime UAF during format-change stop
In the Linux kernel, the following vulnerability has been resolved: ALSA: aloop: Fix peer runtime UAF during format-change stop loopback_check_format() may stop the capture side when playback starts with parameters that no longer match a running capture stream. Commit 826af7fa62e3 ("ALSA: aloop: Fix racy access at PCM trigger") moved the peer lookup under cable->lock, but the actual snd_pcm_stop() still runs after dropping that lock. A concurrent close can clear the capture entry from cable->streams[] and detach or free its runtime while the playback trigger path still holds a stale peer substream pointer. Keep a per-cable count of in-flight peer stops before dropping cable->lock, and make free_cable() wait for those stops before detaching the runtime. This preserves the existing behavior while making the peer runtime lifetime explicit.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.1% (30-day exploitation probability)+0
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 597603d615d2b19a9e451d8cfac24372856a522d and < 83bd62fa9620ac98d5d694bde14c50f98c8e7189≥ 597603d615d2b19a9e451d8cfac24372856a522d and < 345c24b2bcf0923dfae1ab41497351c68214ff76≥ 597603d615d2b19a9e451d8cfac24372856a522d and < 3727a3541788412c393eec236ad228d72efe19c7≥ 597603d615d2b19a9e451d8cfac24372856a522d and < d258cdce50ff3e02392917258e81a0ce9555c327≥ 597603d615d2b19a9e451d8cfac24372856a522d and < 03f52a9c170431e8f10e156b9dc0dae80b3e9198≥ 597603d615d2b19a9e451d8cfac24372856a522d and < bdd9503c3d222d2735b56c7a8b4422ccf3de6e5c≥ 597603d615d2b19a9e451d8cfac24372856a522d and < 5d45e34bf001344e2966dabca1897561bbc9e913≥ 597603d615d2b19a9e451d8cfac24372856a522d and < e5c33cdc6f402eab8abd36ecf436b22c9d3a8aff and 1 moreversion 2.6.37 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel | ≥ 2.6.37 and < 5.10.259≥ 5.11 and < 5.15.210≥ 5.16 and < 6.12.88≥ 6.13 and < 6.18.27≥ 6.19 and < 7.0.4version 7.1-rc1 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
| 7.0 | CVSS 3.1 | High | 1.0 | 5.9 | 0b0ca135-0b70-47e7-9f44-1890c2a1c46c via NIST National Vulnerability Database |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.14%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- Fix documented
- CVSS changed · 7.8
- Source status changed · → Modified
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
25 on the record
- git.kernel.org/stable/c/83bd62fa9620ac98d5d694bde14c50f98c8e7189
- git.kernel.org/stable/c/bdd9503c3d222d2735b56c7a8b4422ccf3de6e5c
- git.kernel.org/stable/c/345c24b2bcf0923dfae1ab41497351c68214ff76
- git.kernel.org/stable/c/03f52a9c170431e8f10e156b9dc0dae80b3e9198
- git.kernel.org/stable/c/e5c33cdc6f402eab8abd36ecf436b22c9d3a8aff
- git.kernel.org/stable/c/5d45e34bf001344e2966dabca1897561bbc9e913
- access.redhat.com/errata/RHSA-2026:27353
- access.redhat.com/errata/RHSA-2026:34094
- access.redhat.com/errata/RHSA-2026:33900
- access.redhat.com/errata/RHSA-2026:33215
- access.redhat.com/errata/RHSA-2026:34443
- access.redhat.com/errata/RHSA-2026:41236
- git.kernel.org/stable/c/3727a3541788412c393eec236ad228d72efe19c7
- access.redhat.com/errata/RHSA-2026:33899
- access.redhat.com/errata/RHSA-2026:35896
- access.redhat.com/errata/RHSA-2026:35844
- access.redhat.com/security/cve/CVE-2026-46090
- access.redhat.com/errata/RHSA-2026:34095
- access.redhat.com/errata/RHSA-2026:35863
- access.redhat.com/errata/RHSA-2026:33685
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-46090.json
- bugzilla.redhat.com/show_bug.cgi
- git.kernel.org/stable/c/d258cdce50ff3e02392917258e81a0ce9555c327
- access.redhat.com/errata/RHSA-2026:27354
- access.redhat.com/errata/RHSA-2026:30848
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 9h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 9h
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-46090 is "ALSA: aloop: Fix peer runtime UAF during format-change stop", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.10% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.