CVE-2025-38635

What it actually does

Missing NULL check after devm_kasprintf() in davinci_lpsc_clk_register() causes NULL pointer dereference on memory allocation failure in the Linux kernel clk davinci driver.

Why it matters to the business

Potential kernel instability or crashes affecting DaVinci-based systems and downstream Chainguard container images with 431 days of exposure and noted ecosystem prevalence in openjdk-17-openj9 packages.

How an attack unfolds

An attacker forces a memory allocation failure while triggering davinci_lpsc_clk_register(), dereferencing NULL to crash the kernel; related Linux kernel privilege escalation patterns observed in container-optimized OS environments by listed threat actors could be adapted if the dereference yields control flow.

How to fix it

Upgrade to fixed versions: openjdk-17-openj9 (Chainguard) 0.53.0-r0 and equivalents for dbg/default-jdk/default-jvm/default-policy/doc/jmods/jre variants; Linux kernel to commit 77e9ad7a2d0e2a771c9e0be04b9d1639413b5f13.

How to confirm the fix worked

Confirm package versions match listed fixed releases, then exercise davinci_lpsc_clk_register() under simulated allocation failure to verify absence of dereference.

Typical attack path

1. Force low-memory condition on target system
2. Invoke davinci_lpsc_clk_register() path
3. Trigger NULL dereference from unchecked devm_kasprintf() result
4. Exploit resulting crash for denial of service or potential escalation

How to detect it

Inspect kernel logs and oops/panic traces for references to davinci_lpsc_clk_register or devm_kasprintf failures; correlate with container runtime events on affected Chainguard images.

What your security team should do

• Apply listed package and kernel upgrades immediately given 431 days since publication and EPSS trend increase
• Prioritize Chainguard openjdk-17-openj9 images and DaVinci kernel deployments
• Review container-optimized OS environments for related privilege escalation activity