Linux kernel drm/ttm: resource leak on eviction error paths other than -EMULTIHOP
Impact
TTM is the buffer-object memory manager shared by the amdgpu, nouveau and radeon DRM drivers. On an eviction failure returning anything other than -EMULTIHOP, the resource is leaked. On a GPU node this accrues inside the kernel's accounting of device memory as tenants churn buffer objects, and in the long run can leave VRAM or GTT accounted as in-use with no owner, degrading or failing allocations until the node is rebooted. The record describes a leak only - no memory-disclosure or code-execution path is shown.
Who can reach it
Local user with access to a DRM render node (/dev/dri/renderD*) that uses TTM - that is, any tenant with a GPU pod on an AMD or nouveau node. Authentication to the host is required; no remote path.
What to do
Update to a stable kernel carrying the drm/ttm fix (commits 6aea0032380b, 7738335d73d0, e8188c461ee0, e9c44738cb1f) and reboot each GPU node; the DRM driver cannot be reloaded under live GPU workloads, so this is a drain-and-reboot. No mitigation short of patching is described.
References
Related entries
- GPU Display Driver: Local privesc (kernel buffer over-read)CVE-2024-0071 · GPU Display DriverHigh
- GPU Display Driver: Local privesc (improper privilege management)CVE-2024-0073 · GPU Display DriverHigh
- vGPU Manager: Guest-to-host privesc (improper privilege management)CVE-2024-0077 · vGPU ManagerHigh
- vGPU Manager: Guest-to-host privescCVE-2024-0084 · vGPU ManagerHigh
- GPU Display Driver: Local privesc (improper resource validation / uninit memory)CVE-2024-0089 · GPU Display DriverHigh
- GPU Display Driver: Local privesc to host root (OOB write)CVE-2024-0090 · GPU Display DriverHigh
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.