CVE-2026-64008 Linux CVE debrief

Who should care

Linux kernel developers and maintainers, Linux distribution vendors, and users of Linux-based systems should be aware of this vulnerability and take steps to mitigate it. This includes reviewing and applying kernel patches, inventorying Linux kernel versions and configurations to identify potentially affected systems, and monitoring for potential exploitation attempts using the Rocket IOCTL create_bo function.

Technical summary

The Linux kernel's Rocket IOCTL create_bo function creates a GEM handle early and inserts it into the file's IDR. However, if certain operations (sgt allocation, drm_mm insert, iommu_map) fail after the handle is live, the error path calls drm_gem_shmem_object_free(), which frees the object without removing the handle from the IDR. This leaves a dangling handle pointing to freed slab memory, allowing for use-after-free (UAF) attacks. The fix moves drm_gem_handle_create() to after all fallible operations succeed, matching the pattern used by panfrost, lima, and etnaviv. Additionally, the return value of drm_mm_insert_node_generic() was silently overwritten by iommu_map_sgtable() and a missing error check was added.

Defensive priority

High

Recommended defensive actions

• Review and apply the provided kernel patches to fix the vulnerability
• Inventory Linux kernel versions and configurations to identify potentially affected systems
• Monitor for potential exploitation attempts using the Rocket IOCTL create_bo function
• Implement compensating controls, such as memory protection mechanisms, to reduce the attack surface
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed

Evidence notes

The CVE record was published on 2026-07-19T16:17:40.557Z and has not been modified since then. The NVD entry is currently Received. The vulnerability was resolved in the Linux kernel by moving drm_gem_handle_create() to after all fallible operations succeed.

Official resources