GHSA-5CM7-74MX-P47M
Vulnerability from github – Published: 2026-10-23 15:31 – Updated: 2026-10-23 15:31In 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": [],
"aliases": [
"CVE-2026-98949"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-23T13:17:16Z",
"severity": null
},
"details": "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\u0027s 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-\u003egpuvm_bo, the new object\u0027s\n vm_bo:\n\n prev_va --obj--\u003e BO_A BO_B \u003c--obj-- vm_bo (ctx-\u003egpuvm_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-\u003eobj)\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-\u003eremap.unmap-\u003eva-\u003evm_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.",
"id": "GHSA-5cm7-74mx-p47m",
"modified": "2026-10-23T15:31:32Z",
"published": "2026-10-23T15:31:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98949"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/196d4d10c1b33ae176685ff42a9994a5952b1d0f"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/521cf8403a185a9d5790fe324bb43ba7ea85f51c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/784356aa88b82035d70e9faeded49b70cddeb29e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9caa2eca5cc8372517ff36a83f321d4326abae93"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.