CVE-2023-54096

What it actually does

Broken completion signaling in soundwire enumeration fails to wake all current and future waiters and uses incorrect reinitialization, enabling memory corruption when waiters remain on the queue.

Why it matters to the business

Audio devices may fail to initialize or resume correctly, causing deferred probes, runtime PM timeouts, and potential kernel instability on affected Linux systems.

How an attack unfolds

An attacker with local access triggers repeated soundwire device attach/detach or suspend/resume cycles; the faulty completion handling leaves waiters unsignaled and corrupts memory structures when the queue is reinitialized while occupied.

How to fix it

Update the Linux kernel to the commit 48d1d0ce0782f995fda678508fdae35c5e9593f0 or later stable release containing the soundwire enumeration fix.

How to confirm the fix worked

Confirm the running kernel contains commit 48d1d0ce0782f995fda678508fdae35c5e9593f0; verify soundwire device probe and resume complete without timeouts under load.

Typical attack path

1. Obtain local execution on a system with soundwire hardware
2. Trigger device enumeration or runtime PM resume paths that block on the broken completions
3. Force repeated reprobe or suspend/resume sequences to exercise the signaling and reinitialization flaw
4. Trigger memory corruption via remaining waiters on the queue

How to detect it

Review kernel logs for soundwire enumeration timeouts, completion-related warnings, or memory corruption oops during device probe and resume; correlate with sound card driver activity.

What your security team should do

• Apply the fixed kernel commit immediately on all systems exposing soundwire devices
• Prioritize audio and embedded platforms where runtime PM and deferred probing are active
• Monitor for kernel oops or memory corruption reports in soundwire paths until patched