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.
Published: 2026-10-23
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Memory corruption from out‑of‑bounds array write
Action: Patch Now
AI Analysis

Impact

A bug in the Linux kernel’s ASoC qcom lpass‑cpu driver uses the DAI (digital audio interface) ID as an array index when configuring playback constraints for the QUAD01 mode. Since the DAI ID is a hardware port identifier, it may not match the array position, causing the code to write beyond the bounds of the dai_driver table. This out‑of‑bounds write can corrupt kernel memory, potentially leading to a crash or, in the worst case, kernel code execution.

Affected Systems

All Linux kernel builds that include the ASoC qcom lpass‑cpu driver and run on platforms with sparse DAI IDs, for example IPQ806x MI2S devices. The vulnerability is triggered when the hardware is configured for LPAIF_I2SCTL_MODE_QUAD01 and the probe path uses the incorrect index.

Risk and Exploitability

The vulnerability results in a kernel memory corruption condition that could cause a crash or, in the worst case, kernel code execution. The CVSS score of 5.5 indicates moderate severity, and the EPSS score of < 1% shows a very low current exploitation probability. The flaw is not listed in the CISA KEV catalog. The attack vector is a local kernel‑level fault during driver initialization and does not require external network access.

Generated by OpenCVE AI on October 29, 2026 at 22:00 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the kernel patch from the commits referenced in the advisory, rebuilding or installing the updated kernel.
  • Reboot the system to load the patched kernel and ensure the fix takes effect.
  • If an updated kernel cannot be applied immediately, temporarily disable the QUAD01 configuration for the MI2S DAI to prevent the out‑of‑bounds write.

Generated by OpenCVE AI on October 29, 2026 at 22:00 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Ubuntu USN Ubuntu USN USN-9018-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9018-2 Linux kernel (HWE) vulnerabilities
Ubuntu USN Ubuntu USN USN-9019-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9020-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9022-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9023-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9024-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9025-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9026-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9039-1 Linux kernel (Azure CVM) vulnerabilities
Ubuntu USN Ubuntu USN USN-9040-1 Linux kernel (Low Latency NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9066-1 Linux kernel (HWE) vulnerabilities
History

Fri, 30 Oct 2026 13:00:00 +0000


Thu, 29 Oct 2026 20:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-20
CWE-788

Thu, 29 Oct 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-787
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


Fri, 23 Oct 2026 21:30:00 +0000

Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux

Fri, 23 Oct 2026 17:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-20
CWE-788

Fri, 23 Oct 2026 12:30:00 +0000

Type Values Removed Values Added
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.
Title ASoC: qcom: lpass-cpu: use DAI table index for playback constraints
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-30T12:40:27.052Z

Reserved: 2026-09-25T10:25:14.381Z

Link: CVE-2026-98940

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-23T13:17:14.960

Modified: 2026-10-30T13:21:32.277

Link: CVE-2026-98940

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-10-23T12:12:08Z

Links: CVE-2026-98940 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-29T22:15:04Z

Weaknesses