VulnerabilityPublished 23 Oct 2026

CVE-2026-98949: Linux kernel · drm/imagination: Fix reference and vm_bo handling in remap()

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in 784356aa88b82035d70e9faeded49b70cddeb29e : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:18 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 784356aa88b82035d70e9faeded49b70cddeb29e, 521cf8403a185a9d5790fe324bb43ba7ea85f51c, 196d4d10c1b33ae176685ff42a9994a5952b1d0f +1

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to 784356aa88b82035d70e9faeded49b70cddeb29e, 521cf8403a185a9d5790fe324bb43ba7ea85f51c, 196d4d10c1b33ae176685ff42a9994a5952b1d0f or 9caa2eca5cc8372517ff36a83f321d4326abae93.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ ff5f643de0bf27874c4033cd57a0bd034b5c7d11, < 784356aa88b82035d70e9faeded49b70cddeb29e	Fixed in 784356aa88b82035d70e9faeded49b70cddeb29e
LinuxLinux	Affected ≥ ff5f643de0bf27874c4033cd57a0bd034b5c7d11, < 521cf8403a185a9d5790fe324bb43ba7ea85f51c	Fixed in 521cf8403a185a9d5790fe324bb43ba7ea85f51c
LinuxLinux	Affected ≥ ff5f643de0bf27874c4033cd57a0bd034b5c7d11, < 196d4d10c1b33ae176685ff42a9994a5952b1d0f	Fixed in 196d4d10c1b33ae176685ff42a9994a5952b1d0f
LinuxLinux	Affected ≥ ff5f643de0bf27874c4033cd57a0bd034b5c7d11, < 9caa2eca5cc8372517ff36a83f321d4326abae93	Fixed in 9caa2eca5cc8372517ff36a83f321d4326abae93
LinuxLinux	Affected =6.8	Fixed in–

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.

References

Community reviews

Loading reviews…