CVE-2025-38160

What it actually does

Missing NULL check after devm_kasprintf() in raspberrypi_clk_register() causes NULL pointer dereference on memory allocation failure, resulting in kernel memory corruption.

Why it matters to the business

Kernel crashes or instability on Linux systems using Raspberry Pi clock drivers, leading to downtime and potential privilege escalation paths in containerized environments.

How an attack unfolds

An attacker triggers memory allocation failure during module registration in the bcm rpi clock driver; the unchecked NULL return from devm_kasprintf() is dereferenced, enabling crash or escalation. Listed threat actors have demonstrated similar Linux kernel privilege escalation techniques in container-optimized OS and spyware campaigns.

How to fix it

Apply the upstream fix by updating to Linux kernel commit 938f625bd3364cfdc93916739add3b637ff90368. For sdl2 on Mageia 8 upgrade to version 2.0.14-1.1.mga8.

How to confirm the fix worked

Inspect the raspberrypi_clk_register function source to confirm a NULL check immediately follows the devm_kasprintf call; test registration under memory-constrained conditions.

Typical attack path

1. Induce memory pressure to force devm_kasprintf failure in raspberrypi_clk_register
2. Trigger NULL pointer dereference in the clock registration path
3. Exploit resulting memory corruption for denial of service or privilege escalation

How to detect it

Review kernel logs for oops/panic entries mentioning raspberrypi_clk_register, devm_kasprintf, or NULL dereference in clk bcm rpi; correlate with container startup events.

What your security team should do

• Prioritize kernel updates to the fixed commit across all affected distributions
• Monitor container workloads for clock driver related oops or panics given listed threat actor activity
• Harden memory allocation paths and review container privilege boundaries