{"id":"CVE-2026-98940","title":"ASoC: qcom: lpass-cpu: use DAI table index for playback constraints","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: qcom: lpass-cpu: use DAI table index for playback constraints\n\nThe DAI ID is a hardware port ID and is not necessarily the index of\nthe corresponding entry in var…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= c223f41c1a52bfe10f1d3311679b1d1f9813e500 < 775df6a27e8433e2414124472938009b958f9a77","Linux >= c223f41c1a52bfe10f1d3311679b1d1f9813e500 < 6833f1893ac2ec40016c348779af63debf3700d2","Linux >= c223f41c1a52bfe10f1d3311679b1d1f9813e500 < 69d2b7a4c115181629eb14d800aecc3e7de3f7fb","Linux >= c223f41c1a52bfe10f1d3311679b1d1f9813e500 < f11336e6d3cd9e28e5cdf1cb8a6171e7c3eff4e4","Linux >= c223f41c1a52bfe10f1d3311679b1d1f9813e500 < ca51771c8efde5df05476ac98dd1b2af4e2b149f","Linux 5.14"],"published":"2026-10-23","updated":"2026-10-23","sourceUpdated":"2026-10-23T12:12:08.487Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-98940","references":[{"url":"https://git.kernel.org/stable/c/775df6a27e8433e2414124472938009b958f9a77"},{"url":"https://git.kernel.org/stable/c/6833f1893ac2ec40016c348779af63debf3700d2"},{"url":"https://git.kernel.org/stable/c/69d2b7a4c115181629eb14d800aecc3e7de3f7fb"},{"url":"https://git.kernel.org/stable/c/f11336e6d3cd9e28e5cdf1cb8a6171e7c3eff4e4"},{"url":"https://git.kernel.org/stable/c/ca51771c8efde5df05476ac98dd1b2af4e2b149f"}],"tags":["cve.org"],"ingestedAt":"2026-10-23T13:24:55.562Z","slug":"CVE-2026-98940","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: qcom: lpass-cpu: use DAI table index for playback constraints\n\nThe DAI ID is a hardware port ID and is not necessarily the index of\nthe corresponding entry in variant->dai_driver.\n\nWhen configuring a DAI with LPAIF_I2SCTL_MODE_QUAD01, the probe code\ncurrently uses dai_id to index variant->dai_driver. This is incorrect\nfor platforms where DAI IDs are sparse. For example, the IPQ806x MI2S\nDAI has ID 4 while it is the only entry in the DAI driver table. If\nthat DAI is configured for QUAD01 and probe reaches this branch, the\ncode writes beyond that single entry via dai_driver[4] instead of\nupdating the DAI being processed.\n\nUse the loop index i when updating the current DAI's playback channel\nconstraints, while retaining dai_id for indexing the hardware-port\nspecific playback SD-line mode array.\n\nThis fixes the incorrect DAI table access for platforms where the DAI\nID does not match its position in the driver table.\n\n## Affected\n\n- `Linux >= c223f41c1a52bfe10f1d3311679b1d1f9813e500 < 775df6a27e8433e2414124472938009b958f9a77`\n- `Linux >= c223f41c1a52bfe10f1d3311679b1d1f9813e500 < 6833f1893ac2ec40016c348779af63debf3700d2`\n- `Linux >= c223f41c1a52bfe10f1d3311679b1d1f9813e500 < 69d2b7a4c115181629eb14d800aecc3e7de3f7fb`\n- `Linux >= c223f41c1a52bfe10f1d3311679b1d1f9813e500 < f11336e6d3cd9e28e5cdf1cb8a6171e7c3eff4e4`\n- `Linux >= c223f41c1a52bfe10f1d3311679b1d1f9813e500 < ca51771c8efde5df05476ac98dd1b2af4e2b149f`\n- `Linux 5.14`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}