CVE-2021-47381

What it actually does

Incorrect @buf argument passed to hex_dump_to_buffer() and erroneous stack address used in DSP oops error output, resulting in disclosure of unintended memory contents in logs.

Why it matters to the business

Minimal operational disruption limited to error logging paths in audio DSP handling; low likelihood of sensitive data exposure under specific failure conditions.

How an attack unfolds

An attacker triggers a DSP oops condition in the SOF audio subsystem and examines the resulting error dump output to obtain memory contents that were incorrectly addressed or buffered.

How to fix it

Apply the kernel patch resolving the hex_dump_to_buffer argument and stack address usage in ASoC SOF DSP dump functions.

How to confirm the fix worked

Confirm presence of the fix in kernel source for SOF oops handling; reproduce DSP error conditions and verify correct buffer and address usage in dumps.

Typical attack path

1. Cause DSP oops error condition via crafted audio operations or faults
2. Capture kernel error logs containing the stack dump output
3. Analyze dump contents for unintended memory disclosure

How to detect it

Inspect kernel logs and dmesg for DSP oops messages; look for stack dumps referencing incorrect addresses or buffers.

What your security team should do

• Apply kernel updates containing the ASoC SOF fix
• Review audio subsystem error logging configurations
• Monitor EPSS and exploit maturity indicators for changes