{"id":"CVE-2024-53080","state":"PUBLISHED","title":"drm/panthor: Lock XArray when getting entries for the VM","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/panthor: Lock XArray when getting entries for the VM\n\nSimilar to commit cac075706f29 (\"drm/panthor: Fix race when converting\ngroup handle to group object\") we need to use the XArray's internal\nlocking when retrieving a vm pointer from there.\n\nv2: Removed part of the patch that was trying to protect fetching\nthe heap pointer from XArray, as that operation is protected by\nthe @pool->lock.","publishedAt":"2024-11-19T17:45:10.820Z","updatedAt":"2026-08-05T11:43:30.489Z","severity":{"score":7.8,"label":"High","version":"3.1","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","source":"Linux"},"assigner":"Linux","products":["Linux Linux"],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"647810ec247641eb5aec8caef818919a4518a0b1","status":"affected","lessThan":"3342f066a8e1020a6f7d1fbd6b23bfdeda473eb5","versionType":"git"},{"version":"647810ec247641eb5aec8caef818919a4518a0b1","status":"affected","lessThan":"444fa5b100e5c90550d6bccfe4476efb0391b3ca","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/gpu/drm/panthor/panthor_mmu.c"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"6.10","status":"affected"},{"version":"0","status":"unaffected","lessThan":"6.10","versionType":"semver"},{"version":"6.11.8","status":"unaffected","lessThanOrEqual":"6.11.*","versionType":"semver"},{"version":"6.12","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/gpu/drm/panthor/panthor_mmu.c"]}],"references":["https://git.kernel.org/stable/c/3342f066a8e1020a6f7d1fbd6b23bfdeda473eb5","https://git.kernel.org/stable/c/444fa5b100e5c90550d6bccfe4476efb0391b3ca","https://project-zero.issues.chromium.org/issues/377500597"],"weaknesses":[],"ingestedAt":"2026-10-29T20:08:04.920Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2024/53xxx/CVE-2024-53080.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2024-53080","state":"PUBLISHED","datePublished":"2024-11-19T17:45:10.820Z","dateUpdated":"2026-08-05T11:43:30.489Z","assignerShortName":"Linux","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateReserved":"2024-11-19T17:17:24.977Z"},"containers":{"cna":{"title":"drm/panthor: Lock XArray when getting entries for the VM","descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/panthor: Lock XArray when getting entries for the VM\n\nSimilar to commit cac075706f29 (\"drm/panthor: Fix race when converting\ngroup handle to group object\") we need to use the XArray's internal\nlocking when retrieving a vm pointer from there.\n\nv2: Removed part of the patch that was trying to protect fetching\nthe heap pointer from XArray, as that operation is protected by\nthe @pool->lock."}],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"647810ec247641eb5aec8caef818919a4518a0b1","status":"affected","lessThan":"3342f066a8e1020a6f7d1fbd6b23bfdeda473eb5","versionType":"git"},{"version":"647810ec247641eb5aec8caef818919a4518a0b1","status":"affected","lessThan":"444fa5b100e5c90550d6bccfe4476efb0391b3ca","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/gpu/drm/panthor/panthor_mmu.c"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"6.10","status":"affected"},{"version":"0","status":"unaffected","lessThan":"6.10","versionType":"semver"},{"version":"6.11.8","status":"unaffected","lessThanOrEqual":"6.11.*","versionType":"semver"},{"version":"6.12","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/gpu/drm/panthor/panthor_mmu.c"]}],"references":[{"url":"https://git.kernel.org/stable/c/3342f066a8e1020a6f7d1fbd6b23bfdeda473eb5"},{"url":"https://git.kernel.org/stable/c/444fa5b100e5c90550d6bccfe4476efb0391b3ca"},{"url":"https://project-zero.issues.chromium.org/issues/377500597"}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - The vulnerability is reached only through ioctls on the panthor DRM render node (/dev/dri/renderD*), requiring local access to the device file. No network or remote path exists.\nAC:L - The attacker controls both sides of the race entirely — one thread loops on VM_DESTROY while another loops on VM_GET_STATE/VM_BIND/TILER_HEAP_CREATE/GROUP_CREATE with the same handle on the same drm_file — and can retry indefinitely at no cost while arranging the VM to hold exactly one reference so the destroy frees it.\nPR:L - All involved ioctls are DRM_RENDER_ALLOW, so any local user or sandboxed application with render-node access (standard for Android apps, the Chrome GPU process, and desktop sessions on Mali CSF hardware) can trigger it. No capabilities or root are required.\nUI:N - The attacking process performs both racing ioctls itself; no victim action, mount, or file open by another user is needed.\nS:U - The corruption is confined to kernel memory within the same security authority; there is no VM, IOMMU, or hypervisor boundary crossed.\nC:H - The use-after-free lets the attacker reclaim the freed panthor_vm slot with sprayed data and have the kernel read it back (vm->unusable, heaps.pool, gpuvm ops), and a group holding the freed VM keeps using its io-pgtable state, enabling disclosure of kernel memory.\nI:H - The racing kref_get performs a refcount_inc write into freed, attacker-reclaimable heap memory, and drm_gpuvm_free() later dispatches through gpuvm->ops->vm_free read from that same reclaimed object, giving write and control-flow-hijack primitives; the extra put also produces a double free.\nA:H - Even unexploited, the UAF and the resulting double free reliably cause refcount warnings, mutex operations on freed memory, and kernel oops/panic, plus dangling GPU page tables — a full denial of service."}]}],"providerMetadata":{"shortName":"Linux","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateUpdated":"2026-08-05T11:43:30.489Z"},"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.10","versionEndExcluding":"6.11.8"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.10","versionEndExcluding":"6.12"}]}]}],"x_generator":{"engine":"bippy-1.2.0"}}}}}