CVE-2025-38645

What it actually does

Missing NULL pointer check before accessing device memory in mlx5 driver allows null dereference and kernel crash when dev->dm allocation fails in mlx5_init_once().

Why it matters to the business

Potential denial of service through system crashes on Linux hosts using MLX5 network hardware, increasing operational downtime risk in network-intensive environments despite low exploitation probability.

How an attack unfolds

An attacker triggers a failure condition during mlx5 driver initialization that leaves the device memory pointer unallocated, then induces subsequent code paths to dereference it, resulting in a kernel panic; context of related container and kernel privilege escalation activity noted but no confirmed active campaigns for this issue.

How to fix it

Upgrade Linux kernel to commit 9053a69abfb5680c2a95292b96df5d204bc0776f or affected Chainguard OpenJDK packages to version 0.53.0-r0 and later.

How to confirm the fix worked

Confirm presence of the added NULL check in mlx5 driver source or verify running kernel and package versions match fixed releases.

Typical attack path

1. Cause mlx5_init_once allocation of dev->dm to fail
2. Trigger code paths that access the unchecked device memory pointer
3. Induce kernel panic or crash

How to detect it

Search kernel logs and dmesg for oops/panic entries referencing mlx5 and device memory pointer access failures around driver initialization.

What your security team should do

• Prioritize kernel and package updates on all systems using MLX5 devices
• Review boot and driver initialization logs for allocation failures
• Test updates in staging before broad deployment given ecosystem prevalence in Linux distributions