CVE-2024-46699

What it actually does

Race condition in the v3d GPU driver where preemption is not disabled around write_seqcount_begin/end calls when updating GPU statistics, allowing concurrent modification and triggering seqlock assertions during job scheduling.

Why it matters to the business

Linux systems using Broadcom V3D graphics hardware may experience kernel warnings, potential instability in graphics workloads, or degraded performance; widespread kernel deployment increases exposure for servers and embedded devices.

How an attack unfolds

An attacker with local access triggers repeated GPU job submissions that race with preemption events, hitting the unprotected seqcount section and causing assertion failures or unexpected scheduler behavior.

How to fix it

Upgrade the Linux kernel to version 6.10.8 or later; apply commit 1e93467ef20308da5a94cde548ee17d523e8ba7b on stable branches; rebuild and reboot with the patched kernel.

How to confirm the fix worked

Confirm the running kernel contains the fix by checking /proc/version or the applied commit; reproduce GPU job workloads under load and verify absence of the seqprop_assert warning in dmesg.

Typical attack path

1. Obtain local user access on an affected Linux system with v3d hardware
2. Submit concurrent GPU rendering or compute jobs via the DRM interface
3. Induce preemption during the unprotected stats update window
4. Observe kernel warnings or trigger follow-on scheduler faults

How to detect it

Search kernel logs for the v3d seqprop_assert warning and drm_sched_run_job_work stack traces; correlate with v3d_bin job activity under high preemption load.

What your security team should do

• Prioritize kernel updates on all systems with V3D graphics within the next patch cycle
• Monitor for similar preemption/seqcount patterns in other DRM drivers
• Test graphics workloads in staging before broad deployment of the updated kernel