{"id":"CVE-2026-98949","published":"2026-10-23T13:17:16.037","lastModified":"2026-10-23T13:17:16.037","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/imagination: Fix reference and vm_bo handling in remap()\n\nWhen a map overlaps part of an existing mapping, pvr_vm_gpuva_remap()\nsplits the mapping into prev/next parts covering what the request did\nnot take, instead of creating something new. It gets two things wrong.\n\n- A GEM reference is taken for each part but it's never needed and never\n  dropped, so it leaks one reference per split (remap-next-in-2m in\n  tests/imagination/pvr_vm_map.c):\n\n    CRITICAL: 33558528 bytes of shmem still held after close\n\n- The parts still belong to the original object being split, but\n  pvr_vm_gpuva_remap() links them to ctx->gpuvm_bo, the new object's\n  vm_bo:\n\n    prev_va --obj--> BO_A          BO_B <--obj-- vm_bo (ctx->gpuvm_bo)\n            \\___________link___________/  (mismatch: BO_A != BO_B)\n\n  drm_gpuva_link() catches the mismatch:\n\n    WARNING: drivers/gpu/drm/drm_gpuvm.c:2108 at drm_gpuva_link+0x2ec/0x310\n      drm_WARN_ON(obj != vm_bo->obj)\n    Call trace:\n     drm_gpuva_link\n     pvr_vm_gpuva_remap\n     __drm_gpuvm_sm_map\n     pvr_vm_map\n     pvr_ioctl_vm_map\n\n  Link them to op->remap.unmap->va->vm_bo instead.\n\nThe locking of the GPUVA lists of the other objects touched by a split is\nnot addressed here; it is handled by switching the GPUVM to immediate\nmode.","cvssScore":null,"cvssSeverity":null,"cvssVector":null,"cwes":[],"vendors":[],"products":[],"references":[{"url":"https://git.kernel.org/stable/c/196d4d10c1b33ae176685ff42a9994a5952b1d0f","tags":[]},{"url":"https://git.kernel.org/stable/c/521cf8403a185a9d5790fe324bb43ba7ea85f51c","tags":[]},{"url":"https://git.kernel.org/stable/c/784356aa88b82035d70e9faeded49b70cddeb29e","tags":[]},{"url":"https://git.kernel.org/stable/c/9caa2eca5cc8372517ff36a83f321d4326abae93","tags":[]}],"exploitRefs":[],"hasPoc":false,"ai":null}