CVE-2024-22386

What it actually does

Race condition in exynos_drm_crtc_atomic_disable allows null pointer dereference, resulting in kernel panic or denial of service.

Why it matters to the business

Affected systems can experience sudden crashes or loss of availability, interrupting workloads and requiring restarts.

How an attack unfolds

Local attacker triggers concurrent atomic disable operations on the Exynos DRM crtc to win the race and dereference a null pointer.

How to fix it

Upgrade 1panel-dev/kubepi to commit 808aa4f532151a10abd83f60481de3a7a018d3db or later; rebuild and deploy the updated kernel module.

How to confirm the fix worked

Confirm the fixed commit is present in the source tree and that the race condition has been eliminated via code review or targeted testing.

Typical attack path

1. Obtain local user access on a system using the vulnerable driver
2. Perform concurrent operations that invoke exynos_drm_crtc_atomic_disable
3. Exploit timing window to reach null pointer dereference
4. Trigger kernel panic or DoS

How to detect it

Search kernel logs and crash dumps for references to exynos_drm_crtc_atomic_disable combined with null pointer dereference messages.

• exynos_drm_crtc_atomic_disable
• NULL pointer dereference in drm/exynos

What your security team should do

• Apply the referenced commit to all affected builds immediately
• Monitor kernel logs for panics involving exynos_drm
• Limit local access on systems exposing the Exynos DRM driver