CVE-2026-98949
Last modified
CVE-2026-98949 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: drm/imagination: Fix reference and vm_bo handling in remap() When a map overlaps part of an existing mapping, pvr_vm_gpuva_remap() splits the mapping into prev/next parts covering what the request did not take, instead of creating something new. It gets two things wrong. - A GEM reference is taken for each part but it's never needed and never dropped, so it leaks one reference per split (remap-next-in-2m in tests/imagination/pvr_vm_map.c): CRITICAL: 33558528 bytes of shmem still held after close - The parts still belong to the original object being split, but pvr_vm_gpuva_remap() links them to ctx->gpuvm_bo, the new object's vm_bo: prev_va --obj--> BO_A BO_B <--obj-- vm_bo (ctx->gpuvm_bo) \___________link___________/ (mismatch: BO_A != BO_B) drm_gpuva_link() catches the mismatch: WARNING: drivers/gpu/drm/drm_gpuvm.c:2108 at drm_gpuva_link+0x2ec/0x310 drm_WARN_ON(obj != vm_bo->obj) Call trace: drm_gpuva_link pvr_vm_gpuva_remap __drm_gpuvm_sm_map pvr_vm_map pvr_ioctl_vm_map Link them to op->remap.unmap->va->vm_bo instead. The locking of the GPUVA lists of the other objects touched by a split is not addressed here; it is handled by switching the GPUVM to immediate mode..
Description
In the Linux kernel, the following vulnerability has been resolved: drm/imagination: Fix reference and vm_bo handling in remap() When a map overlaps part of an existing mapping, pvr_vm_gpuva_remap() splits the mapping into prev/next parts covering what the request did not take, instead of creating something new. It gets two things wrong. - A GEM reference is taken for each part but it's never needed and never dropped, so it leaks one reference per split (remap-next-in-2m in tests/imagination/pvr_vm_map.c): CRITICAL: 33558528 bytes of shmem still held after close - The parts still belong to the original object being split, but pvr_vm_gpuva_remap() links them to ctx->gpuvm_bo, the new object's vm_bo: prev_va --obj--> BO_A BO_B <--obj-- vm_bo (ctx->gpuvm_bo) \___________link___________/ (mismatch: BO_A != BO_B) drm_gpuva_link() catches the mismatch: WARNING: drivers/gpu/drm/drm_gpuvm.c:2108 at drm_gpuva_link+0x2ec/0x310 drm_WARN_ON(obj != vm_bo->obj) Call trace: drm_gpuva_link pvr_vm_gpuva_remap __drm_gpuvm_sm_map pvr_vm_map pvr_ioctl_vm_map Link them to op->remap.unmap->va->vm_bo instead. The locking of the GPUVA lists of the other objects touched by a split is not addressed here; it is handled by switching the GPUVM to immediate mode.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= ff5f643de0bf27874c4033cd57a0bd034b5c7d11, < 521cf8403a185a9d5790fe324bb43ba7ea85f51c; >= ff5f643de0bf27874c4033cd57a0bd034b5c7d11, < 9caa2eca5cc8372517ff36a83f321d4326abae93; >= ff5f643de0bf27874c4033cd57a0bd034b5c7d11, < 784356aa88b82035d70e9faeded49b70cddeb29e; >= ff5f643de0bf27874c4033cd57a0bd034b5c7d11, < 196d4d10c1b33ae176685ff42a9994a5952b1d0f |
| Linux | Linux | 6.8 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98949?
How severe is CVE-2026-98949?
How do I fix CVE-2026-98949?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-98943Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2026-98944In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-98945In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-98946In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98947In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98948In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9895Out of bounds read in GPU in Google Chrome prior to 148.0.77…8.3
- CVE-2026-98950In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98951In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98952In the Linux kernel, the following vulnerability has been re…7.3
- CVE-2026-98953In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98954In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-98949?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
