CVE-2024-42262

What it actually does

Potential memory leak of drm sync objects in the v3d driver when userspace memory fetch fails during performance extension handling due to missing drm_syncobj_put calls.

Why it matters to the business

May lead to gradual memory exhaustion on systems using the v3d graphics driver, potentially causing performance degradation or crashes over time; low prevalence with only 4 downstream dependents reduces widespread operational risk.

How an attack unfolds

An attacker with local access triggers the v3d performance extension, causes a failure in fetching userspace memory during the main loop, resulting in leaked drm_syncobj references without cleanup.

How to fix it

Update the Linux kernel to a version containing commit ad5fdc48f7a63b8a98493c667505fe4d3864ae21 which exports and uses a common cleanup helper for drm_syncobj_put. For luxon (npm) packages, upgrade to versions 1.28.1, 2.5.2, or 3.2.1 where applicable.

How to confirm the fix worked

Inspect kernel source for the exported cleanup helper and its usage in v3d performance extension code; verify memory leak patterns are resolved by testing failure paths in the fetch loop.

Typical attack path

1. Obtain local user access on a system with v3d DRM hardware
2. Interact with the v3d driver to invoke the performance extension
3. Craft input that fails during userspace memory fetch in the main loop
4. Trigger repeated failures to accumulate leaked sync objects

How to detect it

Examine kernel logs for v3d driver errors during performance extension calls; track process memory growth correlated with DRM usage; review for repeated failures in userspace memory fetches without corresponding cleanup.

What your security team should do

• Apply kernel updates containing the fix to all systems with v3d hardware
• Monitor memory usage trends on graphics subsystems in production
• Validate the patch in test environments before broad deployment given the 787 days since publication