Answer in brief
CVE-2026-98940 records a Unknown severity vulnerability in ASoC: qcom: lpass-cpu: use DAI table index for playback constraints. The current sources do not mark it as known exploited. The current feed maps 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.
A CVSS score is not reported in the current record. 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 Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c223f41c1a52bfe10f1d3311679b1d1f9813e500 <775df6a27e8433e2414124472938009b958f9a77 || >=c223f41c1a52bfe10f1d3311679b1d1f9813e500 <6833f1893ac2ec40016c348779af63debf3700d2 || >=c223f41c1a52bfe10f1d3311679b1d1f9813e500 <69d2b7a4c115181629eb14d800aecc3e7de3f7fb || >=c223f41c1a52bfe10f1d3311679b1d1f9813e500 <f11336e6d3cd9e28e5cdf1cb8a6171e7c3eff4e4 || >=c223f41c1a52bfe10f1d3311679b1d1f9813e500 <ca51771c8efde5df05476ac98dd1b2af4e2b149f | 775df6a27e8433e2414124472938009b958f9a77, 6833f1893ac2ec40016c348779af63debf3700d2, 69d2b7a4c115181629eb14d800aecc3e7de3f7fb, f11336e6d3cd9e28e5cdf1cb8a6171e7c3eff4e4, ca51771c8efde5df05476ac98dd1b2af4e2b149f |
| Linux/Linuxgeneric | 5.14 | Not reported |
Published upstream
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 23, 2026
In the Linux kernel, the following vulnerability has been resolved: ASoC: qcom: lpass-cpu: use DAI table index for playback constraints The DAI ID is a hardware port ID and is not necessarily the index of the corresponding entry in variant->dai_driver. When configuring a DAI with LPAIF_I2SCTL_MODE_QUAD01, the probe code currently uses dai_id to index variant->dai_driver. This is incorrect for platforms where DAI IDs are sparse. For example, the IPQ806x MI2S DAI has ID 4 while it is the only entry in the DAI driver table. If that DAI is configured for QUAD01 and probe reaches this branch, the code writes beyond that single entry via dai_driver[4] instead of updating the DAI being processed. Use the loop index i when updating the current DAI's playback channel constraints, while retaining dai_id for indexing the hardware-port specific playback SD-line mode array. This fixes the incorrect DAI table access for platforms where the DAI ID does not match its position in the driver table.
Quoted source text, attributed separately from HOL analysis.