CVE-2024-57880

What it actually does

Out-of-bounds read/write in the Linux kernel ASoC Intel sof_sdw driver caused by accessing one element past the end of a fully populated DAIs array when the initialized member check fails to find a terminator.

Why it matters to the business

Potential kernel crash, privilege escalation, or arbitrary code execution on systems using Intel SoundWire audio configurations; the low EPSS and lack of KEV listing indicate limited observed exploitation but still requires prompt patching on affected kernels.

How an attack unfolds

An attacker crafts or triggers a scenario that fully populates the DAIs array in the sof_sdw driver without a terminator entry, causing the initialized-member check to walk one past the array bounds and access adjacent kernel memory for read or write operations.

How to fix it

Update the Linux kernel to a version containing the fix that adds one extra entry to the DAIs array for the terminator; for the listed chromium-browser packages on Ubuntu 14.04 LTS apply version 58.0.3029.81-0ubuntu0.14.04.1172 or later.

How to confirm the fix worked

Confirm the kernel source contains the expanded DAIs array allocation and terminator handling; verify the chromium-browser package version meets or exceeds 58.0.3029.81-0ubuntu0.14.04.1172 and test audio device enumeration completes without oops or panic.

Typical attack path

1. Identify a system running a vulnerable kernel version with Intel SoundWire audio enabled
2. Trigger full population of the DAIs array through audio device initialization or enumeration
3. Cause the driver to evaluate the initialized member on the out-of-bounds entry
4. Leverage the resulting memory access for information disclosure or corruption

How to detect it

Review kernel logs for ASoC sof_sdw related oops or warnings during audio initialization; inspect dmesg or syslog for array access violations on systems with Intel SoundWire hardware.

What your security team should do

• Prioritize kernel updates on all Intel SoundWire audio systems within the next patching cycle
• Monitor EPSS trend and any new exploit maturity signals for this issue
• Apply the chromium-browser fixed package version 58.0.3029.81-0ubuntu0.14.04.1172 where that component is in use