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

EUVD-2026-45540 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%.

How to fix or mitigate EUVD-2026-45540?

Within 24 hours, inventory all systems running the Linux kernel with amdgpu Video Core Next (VCN) driver support, prioritizing GPU compute clusters and media processing infrastructure; consult your Linux distribution's security advisory for specific affected kernel versions. Within 7 days, obtain and test the available kernel security update in a staging environment to verify GPU workload functionality and compatibility, then create a patching plan for production systems. Within 30 days, deploy the patched kernel across all production systems running amdgpu VCN drivers, confirm via kernel version inventory, and validate GPU driver operation post-deployment.

Linux Kernel EUVD-2026-45540

Q: Which versions of Linux Kernel are affected by EUVD-2026-45540?

Organizations operating GPU-based infrastructure-including AI/ML platforms, scientific computing clusters, and media processing systems-face a privilege escalation risk in the Linux AMD GPU driver…. A patch is available.

| CVE-2026-63856 HIGH

Improper Input Validation (CWE-20)

2026-07-19 Linux

GHSA-g8wx-jx25-gcm6

Information Disclosure Linux

7.8

CVSS 3.1 · Vendor: Linux

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Obtain local GPU render-node access
Delivery

Craft CS submission with 64-bit user fence on VCN 2.0 ring
Exploit

Driver issues unsupported fence write
Execution

Corrupt kernel memory / leak data
Impact

Local privilege escalation or DoS

Vulnerability Assessment

Weakness	CWE CWE-20 OWASP Top 10:2025 A05:2025 - Injection ASVS 5.0 V2 - Validation and Business Logic Input validation, allowlisting
Exploitation Conditions	Exploitation requires local access with the ability to submit GPU command streams (i.e. access to the amdgpu DRM render node /dev/dri/renderD*) on a system equipped with an AMD GPU that uses a VCN v2.0 media engine - the vulnerable path is reached only by issuing a CS submission that requests a 64-bit user fence on the VCN encoder or decoder ring. Limiting factors: the attacker must already be a local user (PR:L, no remote vector), the specific AMD VCN v2.0 hardware and amdgpu driver must be present and in use, and systems without an AMD GPU or without VCN 2.0 rings are not affected; no user interaction and no non-default configuration is otherwise needed once GPU access is granted.
Impact	The CVSS 3.1 vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (base 7.8, HIGH) indicates a local, low-complexity, low-privilege attack with no user interaction and full CIA impact - consistent with a user who already has GPU/render-node access corrupting kernel state. Countervailing signals soften real-world urgency: EPSS is only 0.16% (5th percentile), there is no KEV listing, and no public POC is referenced, so mass exploitation is unlikely. The vendor tag 'Information Disclosure' aligns with the confidentiality impact but the CVSS also asserts high integrity/availability, suggesting memory corruption rather than pure read-only leakage. Note a mild inconsistency to verify: the tag emphasizes info disclosure while the vector claims I:H/A:H - the practical worst case is local memory corruption/DoS, and full arbitrary-code escalation is inferred, not confirmed. Net: legitimate to patch on a normal cadence, but not a drop-everything issue given local-only access and low exploitation probability.
Exploit ScenarioDerived	A local user or a container/process with access to the AMD GPU render node crafts a command-stream submission to a VCN v2.0 encoder or decoder ring that includes a 64-bit user fence request the hardware cannot honor. On an unpatched kernel the driver programs the unsupported fence write, corrupting memory or leaking data and potentially crashing the kernel or escalating privileges. No public POC is referenced, and the low CVSS attack complexity means a knowledgeable local attacker with GPU access could reliably reach the vulnerable path.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

Patch available 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Jul 20, 2026

Local privilege escalation and memory corruption in the Linux kernel's amdgpu VCN (Video Core Next) driver arises because VCN v2.0 encoder and decoder rings accept command-stream (CS) submissions carrying 64-bit user fence writes that the hardware does not actually support. A local user able to submit GPU work (via /dev/dri render nodes) can trigger the driver to perform unsupported fence writes, leading to high-impact confidentiality, integrity, and availability effects consistent with kernel memory corruption or information disclosure. There is no public exploit identified at time of analysis, EPSS is low (0.16%), and the issue is not on the CISA KEV list, so this is a locally-scoped hardening/correctness fix rather than a remotely exploitable emergency.

RemediationAI

Primary fix: update to a patched stable kernel - Vendor-released patch versions 6.6.141, 6.12.91, 6.18.33, 7.0.10, or 7.1 (or later within your series), which set no_user_fence on VCN v2.0 enc/dec rings so the scheduler rejects CS submissions requesting user fences. Apply the corresponding distribution kernel update that incorporates git.kernel.org stable commit f264019be80de79f84f464846451445923bffea0 (and its backports). If immediate patching is not possible, reduce exposure by restricting access to GPU render nodes: tighten permissions/ACLs on /dev/dri/renderD* so only trusted users and services can submit GPU work, and avoid granting untrusted local users or containers direct GPU access - the trade-off is that GPU-accelerated video encode/decode and compute for those users will be unavailable. Verify fixes against your kernel series rather than assuming; the upstream commit hashes above are the source of truth (https://git.kernel.org/stable/c/f264019be80de79f84f464846451445923bffea0).

Affected VersionsENISA

Linux 1b61de45dfaff00b627e47349a019658e39268b9 <ac06ce5cac9e711281585d09d00c6efcd9b86396

Linux patch: 6.18.33

Linux 1b61de45dfaff00b627e47349a019658e39268b9 <c71aecae98e42dcf2baf462df50b3a2cf1a93fe4

Linux patch: 7.0.10

Linux patch: 0

Linux 1b61de45dfaff00b627e47349a019658e39268b9 <5e777bc4cbe928ac0fd95e368fee1540f2ce4db2

Linux 1b61de45dfaff00b627e47349a019658e39268b9 <f264019be80de79f84f464846451445923bffea0

Linux patch: 6.6.141

Linux 5.3

Linux patch: 7.1

Linux patch: 6.12.91

Linux 1b61de45dfaff00b627e47349a019658e39268b9 <8d80b293b41fcb5e9396db93e788b0f4ebcbafb7

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.

Technical ContextAI · show details

The affected component is the AMD GPU (amdgpu) DRM kernel driver, specifically the VCN media engine used for hardware video encode/decode. GPU command submission uses fences to signal completion; a 'user fence' lets the ring write a completion value to a user-supplied memory address. VCN v2.0 enc/dec rings physically cannot perform 64-bit user fence writes, so honoring a user-fence request produces an incorrect/truncated write to a driver- or user-associated address. The fix sets the ring's no_user_fence property so the command scheduler rejects any CS submission that requests a user fence on these rings. CWE is not assigned in the input, but the behavior class is improper validation of a hardware capability leading to an out-of-bounds or malformed memory write (functionally CWE-787-style memory corruption); the CPE data identifies the affected product only as cpe:2.3:a:linux:linux, i.e. the mainline Linux kernel.

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

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 needed (AV:L, PR:L) with no user interaction; malformed hardware fence writes yield kernel memory corruption, so C/I/A all High.

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

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

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/vcn: set no_user_fence for VCN v2.0 enc/dec rings

VCN encoder and decoder rings do not support 64-bit user fence writes, reject CS submissions with user fences.

(cherry picked from commit e2b5499fca55f1a32960a311bbb62e35891eaf73)

Executive ViewAI

Why It Matters

Organizations operating GPU-based infrastructure-including AI/ML platforms, scientific computing clusters, and media processing systems-face a privilege escalation risk in the Linux AMD GPU driver (CVE-2026-63856) that could compromise system integrity and sensitive workload data. An attacker with local system access could exploit this vulnerability to escalate privileges and access protected information. The risk is manageable: patches are available and no public exploit code has been identified at this time.

Business Impact: High

Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score

0.2%

Top 95% exploitable

Prevalence

Ubiquitous

Linux kernel with widely-shipped amdgpu driver for AMD GPUs

Data Quality

5 sources

Confidence: Medium

EUVD

NVD

CVE.org

EPSS Vendor

VulDB

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 HIGH

CISA KEV No

Public POC No

EPSS 0.2%

Patch available Yes

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

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.

SSVC AssessmentENISA

SSVC Decision· derived

Scheduled

Exploitation· derived

None

System Exposure· derived

Small

Automatable· derived

Human Impact

High

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +39

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Information Disclosure MEDIUM

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

Same weakness CWE-20 – Improper Input Validation

View all

CVE-2021-44228 CRITICAL POC

10.0

CVE-2024-3400 CRITICAL POC

10.0

CVE-2022-47966 CRITICAL POC

9.8

CVE-2023-22515 CRITICAL POC

9.8

CVE-2009-0927 HIGH POC

8.8

CVE-2017-9791 CRITICAL POC

9.8

CVE-2017-15944 CRITICAL POC

9.8

CVE-2019-0604 CRITICAL POC

9.8

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-2025-68613 HIGH POC

8.8

CVE-2015-1701 HIGH POC

7.8

CVE-2017-0147 HIGH POC

7.5

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

References

Advisories & patches

ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2026-63856 ADVISORY https://seclists.org/oss-sec/2026/q3/230 ADVISORY https://ubuntu.com/security/notices/USN-8574-1 ADVISORY https://vuldb.com/vuln/380411 REF https://git.kernel.org/stable/c/5e777bc4cbe928ac0fd95e368fee1540f2ce4db2 REF https://git.kernel.org/stable/c/8d80b293b41fcb5e9396db93e788b0f4ebcbafb7 REF https://git.kernel.org/stable/c/ac06ce5cac9e711281585d09d00c6efcd9b86396 REF https://git.kernel.org/stable/c/bcb972496f189edbf56a18b14f9b4831fd127ab8 REF https://git.kernel.org/stable/c/c71aecae98e42dcf2baf462df50b3a2cf1a93fe4 REF https://git.kernel.org/stable/c/f264019be80de79f84f464846451445923bffea0

Search Externally

GitHub PoC

Exploit-DB PacketStorm Snyk Rapid7 Nuclei Templates Trickest PoC

Back