Is there a patch available for EUVD-2026-108923?

Yes, a patch is available for EUVD-2026-108923. Update the affected software to the latest version immediately.

Linux EUVD-2026-108923

| CVE-2026-98949

2026-10-23 Linux

GHSA-5cm7-74mx-p47m

View

Awaiting Data No severity or threat signals available yet. Label will update when CVSS score is published or threat intelligence arrives. Why: No CVSS yet + weak signal (CWE or non-zero EPSS).

Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisCVE.org

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 VersionsENISA

Linux patch: 0

Linux ff5f643de0bf27874c4033cd57a0bd034b5c7d11 <196d4d10c1b33ae176685ff42a9994a5952b1d0f

Linux ff5f643de0bf27874c4033cd57a0bd034b5c7d11 <9caa2eca5cc8372517ff36a83f321d4326abae93

Linux 6.8

Linux ff5f643de0bf27874c4033cd57a0bd034b5c7d11 <784356aa88b82035d70e9faeded49b70cddeb29e

Linux patch: 6.12.113

Linux patch: 7.2.11

Linux patch: 6.18.57

Linux ff5f643de0bf27874c4033cd57a0bd034b5c7d11 <521cf8403a185a9d5790fe324bb43ba7ea85f51c

Linux patch: 7.3

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when the next one hits your stack

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Lifecycle Timeline

Patch available

Oct 23, 2026 - 13:17 EUVD

CVE Published

Oct 23, 2026 - 12:19 cve.org

UNKNOWN (no severity yet)

Threat Intelligence Overview

EPSS Score

0.2%

Top 89% exploitable

Data Quality

1 sources

Confidence: Low

EUVD

CVE.org

EPSS

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity Not scored yet

CISA KEV No

Public POC No

EPSS 0.2%

Patch available Yes

Active threat No

Deciding rule

No CVSS yet + weak signal (CWE or non-zero EPSS)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.