CVE-2026-98940

ASoC: qcom: lpass-cpu: use DAI table index for playback constraints

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.

Key facts

Published
23 Oct 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.173% likely to be exploited in the next 30 days, higher than 6.806% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • c223f41c1a52bfe10f1d3311679b1d1f9813e500 up to but excluding c10823507a74d7474391c01121e3f59901b1789f (affected)
  • c223f41c1a52bfe10f1d3311679b1d1f9813e500 up to but excluding 63987bb73df65fb01245b5905b005aa47c1dd27a (affected)
  • c223f41c1a52bfe10f1d3311679b1d1f9813e500 up to but excluding 775df6a27e8433e2414124472938009b958f9a77 (affected)
  • c223f41c1a52bfe10f1d3311679b1d1f9813e500 up to but excluding 6833f1893ac2ec40016c348779af63debf3700d2 (affected)
  • c223f41c1a52bfe10f1d3311679b1d1f9813e500 up to but excluding 69d2b7a4c115181629eb14d800aecc3e7de3f7fb (affected)
  • c223f41c1a52bfe10f1d3311679b1d1f9813e500 up to but excluding f11336e6d3cd9e28e5cdf1cb8a6171e7c3eff4e4 (affected)
  • c223f41c1a52bfe10f1d3311679b1d1f9813e500 up to but excluding ca51771c8efde5df05476ac98dd1b2af4e2b149f (affected)
LinuxLinux
  • Default status: affected
  • 5.14 (affected)
  • 0 up to but excluding 5.14 (unaffected)
  • 5.15.224 up to and including 5.15.* (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.113 up to and including 6.12.* (unaffected)
  • 6.18.56 up to and including 6.18.* (unaffected)
  • 7.2.10 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 23 Oct 2026 Published

References