Skip to main content
VulnerabilityPublished

CVE-2026-98940: Linux kernel · ASoC: qcom: lpass-cpu: use DAI table index for playback constraints

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in f11336e6d3cd9e28e5cdf1cb8a6171e7c3eff4e4 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:07 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in f11336e6d3cd9e28e5cdf1cb8a6171e7c3eff4e4, ca51771c8efde5df05476ac98dd1b2af4e2b149f, 6833f1893ac2ec40016c348779af63debf3700d2 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ c223f41c1a52bfe10f1d3311679b1d1f9813e500, < f11336e6d3cd9e28e5cdf1cb8a6171e7c3eff4e4
Fixed in
  • f11336e6d3cd9e28e5cdf1cb8a6171e7c3eff4e4
LinuxLinuxAffected
  • ≥ c223f41c1a52bfe10f1d3311679b1d1f9813e500, < ca51771c8efde5df05476ac98dd1b2af4e2b149f
Fixed in
  • ca51771c8efde5df05476ac98dd1b2af4e2b149f
LinuxLinuxAffected
  • ≥ c223f41c1a52bfe10f1d3311679b1d1f9813e500, < 6833f1893ac2ec40016c348779af63debf3700d2
Fixed in
  • 6833f1893ac2ec40016c348779af63debf3700d2
LinuxLinuxAffected
  • ≥ c223f41c1a52bfe10f1d3311679b1d1f9813e500, < 775df6a27e8433e2414124472938009b958f9a77
Fixed in
  • 775df6a27e8433e2414124472938009b958f9a77
LinuxLinuxAffected
  • ≥ c223f41c1a52bfe10f1d3311679b1d1f9813e500, < 69d2b7a4c115181629eb14d800aecc3e7de3f7fb
Fixed in
  • 69d2b7a4c115181629eb14d800aecc3e7de3f7fb
LinuxLinuxAffected
  • =5.14
Fixed in–

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.

References

Community reviews

Loading reviews…