What is the CVSS score of EUVD-2026-45525?

EUVD-2026-45525 has a CVSS 3.1 base score of 7.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.2%.

Which versions of Linux Kernel are affected by EUVD-2026-45525?

AMD GPU JPEG engine (amdgpu driver) contains a memory corruption vulnerability (CVE-2026-63841, CVSS 7.8) that allows authenticated local users to compromise GPU memory confidentiality, integrity,…. A patch is available.

How to fix or mitigate EUVD-2026-45525?

Within 24 hours: Inventory all systems with AMD GPU hardware and document installed amdgpu driver versions. Within 7 days: Obtain and validate the amdgpu driver patch for the JPEG v5.0.1 ring in non-production environments and begin staged deployment. Within 30 days: Complete patch rollout to all production GPU compute infrastructure and verify compliance across the fleet.

Linux Kernel EUVD-2026-45525

| CVE-2026-63841 HIGH

2026-07-19 Linux

GHSA-8cvv-rxg7-8gc2

Information Disclosure Linux

7.8

CVSS 3.1 · Vendor: Linux

Severity by source

Vendor (Linux) PRIMARY

7.8 HIGH

AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

vuln.today AI

7.8 HIGH

Local render-node access with low privileges and no user interaction; unsupported user-fence write on the JPEG ring can leak/corrupt kernel memory and crash the system, giving high C/I/A.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

SUSE

5.5 MEDIUM

AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Red Hat

5.5 MEDIUM

qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 20, 2026 - 15:49 vuln.today

CVSS changed

Jul 20, 2026 - 15:22 NVD

7.8 (HIGH)

Patch available

Jul 19, 2026 - 16:19 EUVD

CVE Published

Jul 19, 2026 - 14:04 cve.org

HIGH 7.8

CVE Published

Jul 19, 2026 - 14:04 cve.org

UNKNOWN (no severity yet)

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.1 ring

JPEG rings do not support 64-bit user fence writes, reject CS submissions with user fences.

(cherry picked from commit 742a98e2e81702df8fe1b1eccee5223220a03dc2)

AnalysisAI

Local privilege-adjacent memory corruption in the Linux kernel's AMD GPU JPEG engine (amdgpu driver, JPEG v5.0.1 ring) allows a local low-privileged user to submit command-stream (CS) submissions containing 64-bit user fences that the JPEG ring cannot service. Because the ring lacks support for user fence writes, accepting such submissions leads to high-impact confidentiality, integrity, and availability consequences (CVSS 7.8). No public exploit identified at time of analysis, and EPSS is very low (0.17%), consistent with a hardware-specific, locally-scoped GPU driver flaw rather than a mass-exploitation target.

Technical ContextAI

The affected component is the amdgpu Direct Rendering Manager (DRM) subsystem, specifically the JPEG decode/encode ring for the JPEG v5.0.1 IP block on AMD GPUs. Userspace submits work to the GPU via command streams (CS) through the DRM ioctl interface; a 'user fence' lets the GPU signal completion by writing a 64-bit value to a userspace-provided address. JPEG rings on this hardware generation do not support 64-bit user fence writes, so a CS submission carrying a user fence causes the driver to attempt an unsupported operation. The fix (cherry-picked from commit 742a98e2e817) sets the ring's no_user_fence flag so the driver rejects CS submissions that request user fences. No CWE was assigned; the tag 'Information Disclosure' and the C:H/I:H/A:H impact point to an unsupported-fence-write path that can corrupt or leak kernel/GPU memory state.

RemediationAI

Vendor-released patch: upgrade to Linux kernel 6.18.33, 7.0.10, or 7.1 (or later), which set no_user_fence for the JPEG v5.0.1 ring and reject CS submissions carrying user fences. Distribution users should apply the corresponding backported kernel package from their vendor and reboot into the patched kernel. The upstream fix commits are available at https://git.kernel.org/stable/c/d0f6ae14c0452be4fc3aa5cf81c74e68b3243050, https://git.kernel.org/stable/c/869ce148c0d953570f8307c3e206b47bd5d3be99, and https://git.kernel.org/stable/c/2f8e3da71a1b469b6e157aa3972f1448b3157840. Where immediate patching is not possible, restrict access to the DRM render nodes (e.g., /dev/dri/renderD*) by tightening group membership and permissions so only trusted users can submit GPU command streams - the trade-off is that this can break unprivileged GPU compute, hardware video/JPEG acceleration, and containerized GPU workloads for those users. On systems that do not need the affected AMD hardware acceleration, disabling or blacklisting the amdgpu JPEG functionality removes exposure but also disables JPEG hardware offload.

Same technique Information Disclosure

View all

CVE-2019-2725 CRITICAL POC

9.8

CVE-2021-34523 CRITICAL POC

9.0

CVE-2013-2251 CRITICAL POC

9.8

CVE-2017-5638 CRITICAL POC

9.8

CVE-2025-24813 CRITICAL POC

9.8

CVE-2015-1701 HIGH POC

7.8

CVE-2017-0147 HIGH POC

7.5

CVE-2014-6324 HIGH POC

8.8

Vendor StatusVendor

SUSE

Severity: Moderate

Product	Status
SUSE Linux Enterprise Desktop 15 SP7	Not-Affected
SUSE Linux Enterprise Desktop 15 SP7	Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7	Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7	Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0	Not-Affected

EUVD-2026-45525 vulnerability details – vuln.today

Back

Linux Kernel EUVD-2026-45525

Severity by source

CVSS VectorVendor: Linux

Lifecycle Timeline

DescriptionCVE.org

AnalysisAI

Technical ContextAI

RemediationAI

Same technique Information Disclosure

Vendor StatusVendor

SUSE

Share

External POC / Exploit Code