Linux kernel out-of-bounds access in Qualcomm LPASS DAI constraints
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c223f41c1a52bfe10f1d3311679b1d1f9813e500 · < f11336e6d3cd9e28e5cdf1cb8a6171e7c3eff4e4| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Qualcomm LPASS CPU audio driver can write beyond its DAI driver table when a platform has sparse DAI IDs and a DAI configured for QUAD01 reaches the affected probe code. The input does not describe how an attacker could trigger this condition or specify access, authentication, or user-interaction requirements.
Engineers running Linux kernels on platforms with sparse DAI IDs that use the Qualcomm LPASS CPU audio driver should check their kernel; affected versions are not specified.