CVE-2024-57799

What it actually does

Race condition allows rk_hdptx_phy_runtime_resume to execute before platform_set_drvdata, causing dev_get_drvdata to return NULL and trigger a kernel NULL pointer dereference.

Why it matters to the business

Systems may experience crashes or instability during hardware initialization on affected Linux kernels; high downstream prevalence increases exposure across many distributions and devices.

How an attack unfolds

An attacker with local access triggers repeated probe or runtime PM events on the samsung-hdptx phy driver during early boot or module load, racing the drvdata assignment and forcing the NULL dereference.

How to fix it

Update to a kernel containing the fix that calls platform_set_drvdata before devm_pm_runtime_enable; for listed chromium-browser packages on Ubuntu 14.04 LTS apply version 58.0.3029.81-0ubuntu0.14.04.1172 or later.

How to confirm the fix worked

Confirm the source change moves platform_set_drvdata ahead of devm_pm_runtime_enable in the probe function; test by exercising runtime PM paths during module initialization and verify absence of NULL dereference.

Typical attack path

1. Gain local execution on target system
2. Trigger driver probe or runtime PM resume for rockchip samsung-hdptx phy
3. Exploit timing window before platform_set_drvdata completes
4. Cause NULL pointer dereference leading to kernel panic or denial of service

How to detect it

Review kernel logs for NULL pointer dereference traces involving rk_hdptx_phy_runtime_resume or samsung-hdptx during probe; correlate with module load timestamps and runtime PM events.

What your security team should do

• Prioritize kernel updates on all systems using the affected phy driver
• Monitor for kernel oops or panic logs referencing rk_hdptx_phy_runtime_resume
• Apply the listed chromium-browser fixed package version where applicable
• Restrict local user access until patches are deployed