Live › vulnerability › CVE-2026-98940
Go to dashboardIn the Linux kernel's Qualcomm LPASS audio driver, the probe code indexed the DAI driver table with a hardware port ID instead of the loop index, so on platforms with sparse DAI IDs it writes past the table entry it should update. The sources do not describe an attacker-triggered exploit path or a confirmed impact beyond this out-of-bounds write.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running Linux kernels with the Qualcomm LPASS CPU audio driver (ASoC qcom lpass-cpu), such as Qualcomm SoC boards like IPQ806x that use MI2S DAIs configured for QUAD01 mode. Systems without these Qualcomm audio components, and general-purpose servers, are unlikely to be affected; the sources do not say more.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-98940")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.