GHSA-H32J-CG7C-PPW6
Vulnerability from github – Published: 2026-10-23 15:31 – Updated: 2026-10-23 15:31In 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.
{
"affected": [],
"aliases": [
"CVE-2026-98940"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-23T13:17:14Z",
"severity": null
},
"details": "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 variant-\u003edai_driver.\n\nWhen configuring a DAI with LPAIF_I2SCTL_MODE_QUAD01, the probe code\ncurrently uses dai_id to index variant-\u003edai_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\u0027s 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.",
"id": "GHSA-h32j-cg7c-ppw6",
"modified": "2026-10-23T15:31:31Z",
"published": "2026-10-23T15:31:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98940"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/6833f1893ac2ec40016c348779af63debf3700d2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/69d2b7a4c115181629eb14d800aecc3e7de3f7fb"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/775df6a27e8433e2414124472938009b958f9a77"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ca51771c8efde5df05476ac98dd1b2af4e2b149f"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f11336e6d3cd9e28e5cdf1cb8a6171e7c3eff4e4"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.