{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98940 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-98940 is a vulnerability in Linux, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-98940 and fix it if it is affected.\n\nWhat it is: CVE-2026-98940 is a vulnerability in Linux, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-98940 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98940/ (Markdown: https://insights.sbomify.com/CVE-2026-98940/index.md)","id":"CVE-2026-98940","markdown":"https://insights.sbomify.com/CVE-2026-98940/index.md","name":"CVE-2026-98940","record":{"aliases":["AZL-110732","BELL-CVE-2026-98940","DEBIAN-CVE-2026-98940","GHSA-h32j-cg7c-ppw6","UBUNTU-CVE-2026-98940"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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'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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"ASoC: qcom: lpass-cpu: use DAI table index for playback constraints","id":"CVE-2026-98940","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"ext4: don't enable large folios on encrypted inodes","id":"CVE-2026-98941"},"packages":[],"prev":{"headline":"x86/mm: Drop unnecessary PMD page copy when freeing","id":"CVE-2026-98939"},"products":["Linux"],"published":"2026-10-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-23","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-98940/"}