Answer in brief
CVE-2026-46090 records a High severity (CVSS 7.8) vulnerability in ALSA: aloop: Fix peer runtime UAF during format-change stop. The current sources do not mark it as known exploited. The current feed maps Red Hat/kernel-rt (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Red Hat/kernel-rt (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Red Hat/kernel-rtgeneric | * | Not reported |
| Linux/Linuxgeneric | >=597603d615d2b19a9e451d8cfac24372856a522d <83bd62fa9620ac98d5d694bde14c50f98c8e7189 || >=597603d615d2b19a9e451d8cfac24372856a522d <345c24b2bcf0923dfae1ab41497351c68214ff76 || >=597603d615d2b19a9e451d8cfac24372856a522d <03f52a9c170431e8f10e156b9dc0dae80b3e9198 || >=597603d615d2b19a9e451d8cfac24372856a522d <bdd9503c3d222d2735b56c7a8b4422ccf3de6e5c || >=597603d615d2b19a9e451d8cfac24372856a522d <5d45e34bf001344e2966dabca1897561bbc9e913 || >=597603d615d2b19a9e451d8cfac24372856a522d <e5c33cdc6f402eab8abd36ecf436b22c9d3a8aff | 83bd62fa9620ac98d5d694bde14c50f98c8e7189, 345c24b2bcf0923dfae1ab41497351c68214ff76, 03f52a9c170431e8f10e156b9dc0dae80b3e9198, bdd9503c3d222d2735b56c7a8b4422ccf3de6e5c, 5d45e34bf001344e2966dabca1897561bbc9e913, e5c33cdc6f402eab8abd36ecf436b22c9d3a8aff |
| Linux/Linuxgeneric | 2.6.37 | Not reported |
| Linux/Linuxgeneric | >=597603d615d2b19a9e451d8cfac24372856a522d <83bd62fa9620ac98d5d694bde14c50f98c8e7189 || >=597603d615d2b19a9e451d8cfac24372856a522d <345c24b2bcf0923dfae1ab41497351c68214ff76 || >=597603d615d2b19a9e451d8cfac24372856a522d <3727a3541788412c393eec236ad228d72efe19c7 || >=597603d615d2b19a9e451d8cfac24372856a522d <d258cdce50ff3e02392917258e81a0ce9555c327 || >=597603d615d2b19a9e451d8cfac24372856a522d <03f52a9c170431e8f10e156b9dc0dae80b3e9198 || >=597603d615d2b19a9e451d8cfac24372856a522d <bdd9503c3d222d2735b56c7a8b4422ccf3de6e5c || >=597603d615d2b19a9e451d8cfac24372856a522d <5d45e34bf001344e2966dabca1897561bbc9e913 || >=597603d615d2b19a9e451d8cfac24372856a522d <e5c33cdc6f402eab8abd36ecf436b22c9d3a8aff | 83bd62fa9620ac98d5d694bde14c50f98c8e7189, 345c24b2bcf0923dfae1ab41497351c68214ff76, 3727a3541788412c393eec236ad228d72efe19c7, d258cdce50ff3e02392917258e81a0ce9555c327, 03f52a9c170431e8f10e156b9dc0dae80b3e9198, bdd9503c3d222d2735b56c7a8b4422ccf3de6e5c, 5d45e34bf001344e2966dabca1897561bbc9e913, e5c33cdc6f402eab8abd36ecf436b22c9d3a8aff |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.