CVE-2026-98940

Unknown

Description

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.

SeverityUnknown
CVSS—
Exploit probability—
ProductLinux
PublishedOct 23, 2026
First seenOct 23, 2026

How to fix

Update
  • Linux Linuxc10823507a74d7474391c01121e3f59901b1789f, 63987bb73df65fb01245b5905b005aa47c1dd27a, 775df6a27e8433e2414124472938009b958f9a77, 6833f1893ac2ec40016c348779af63debf3700d2, 69d2b7a4c115181629eb14d800aecc3e7de3f7fb, f11336e6d3cd9e28e5cdf1cb8a6171e7c3eff4e4, ca51771c8efde5df05476ac98dd1b2af4e2b149f or later

Affected products

ProductAffected versionsFixed in
Linux Linuxc223f41c1a52bfe10f1d3311679b1d1f9813e500 ≤ v < c10823507a74d7474391c01121e3f59901b1789f, c223f41c1a52bfe10f1d3311679b1d1f9813e500 ≤ v < 63987bb73df65fb01245b5905b005aa47c1dd27a, c223f41c1a52bfe10f1d3311679b1d1f9813e500 ≤ v < 775df6a27e8433e2414124472938009b958f9a77, c223f41c1a52bfe10f1d3311679b1d1f9813e500 ≤ v < 6833f1893ac2ec40016c348779af63debf3700d2, c223f41c1a52bfe10f1d3311679b1d1f9813e500 ≤ v < 69d2b7a4c115181629eb14d800aecc3e7de3f7fb, c223f41c1a52bfe10f1d3311679b1d1f9813e500 ≤ v < f11336e6d3cd9e28e5cdf1cb8a6171e7c3eff4e4, c223f41c1a52bfe10f1d3311679b1d1f9813e500 ≤ v < ca51771c8efde5df05476ac98dd1b2af4e2b149f, 5.14c10823507a74d7474391c01121e3f59901b1789f, 63987bb73df65fb01245b5905b005aa47c1dd27a, 775df6a27e8433e2414124472938009b958f9a77, 6833f1893ac2ec40016c348779af63debf3700d2, 69d2b7a4c115181629eb14d800aecc3e7de3f7fb, f11336e6d3cd9e28e5cdf1cb8a6171e7c3eff4e4, ca51771c8efde5df05476ac98dd1b2af4e2b149f

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.