CVE-2024-42298

What it actually does

Unchecked return value from devm_kasprintf() in the Linux kernel fsl_qmc_audio driver can yield a NULL pointer that is later dereferenced, resulting in a kernel NULL pointer dereference.

Why it matters to the business

Systems running affected Linux kernels may experience crashes or instability in audio subsystems under low-memory conditions, potentially leading to denial of service on embedded or audio-processing devices.

How an attack unfolds

An attacker with the ability to trigger the affected code path under memory pressure could cause the kernel to dereference a NULL pointer; however, given the low EPSS score, lack of KEV inclusion, and no known threat actors, practical exploitation remains unlikely without specific local access and environmental conditions.

How to fix it

Update the Linux kernel to a version containing commit b4205dfcfe96182118e54343954827eda51b2135 or later; apply the corresponding stable backports for your distribution.

How to confirm the fix worked

Verify the presence of commit b4205dfcfe96182118e54343954827eda51b2135 in the kernel source tree and confirm that all devm_kasprintf() call sites now include NULL checks.

Typical attack path

1. Gain local access or ability to influence the fsl_qmc_audio driver initialization
2. Induce memory allocation failure during devm_kasprintf() call
3. Trigger subsequent code that dereferences the unchecked NULL return value
4. Cause kernel panic or oops

How to detect it

Review kernel logs for NULL pointer dereference oops messages originating from fsl_qmc_audio; no widespread exploitation indicators exist given the CVE's profile.

What your security team should do

• Prioritize kernel updates on systems using the fsl_qmc_audio driver
• Monitor upstream stable kernel releases for the backported fix
• Test audio functionality after patching to ensure driver stability