EUVD-2026-80418
GHSA-vg7q-4fvq-5g86
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Local GPU-node access (AV:L, PR:L); AC:H because the crafted overflow additionally needs a ~4GiB mapping to pass the prior header check; OOB read discloses memory (C:H) and hangs GPU (A:H), no write primitive (I:N).
Primary rating from Vendor (Linux).
CVSS VectorVendor: Linux
Lifecycle Timeline
6DescriptionCVE.org
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu/vcn: fix integer overflow in dec_msg buffer count check
If the supplied msg[2] (num_buffers) is 0x3FFFFFFF, the expression 6 + num_buffers * 4 wraps to 2 and the bounds check passes, letting the parser loop far past the end of the message BO. Triggering it additionally requires a ~4GiB mapping so that msg[1] survives the earlier "header does not fit in BO" check.
Rewrite the test in division form, which is overflow-free by construction. Also update the message to reflect that msg is invalid.
AnalysisAI
Integer overflow in the Linux kernel's amdgpu VCN decode-message parser lets an authenticated local user with access to the AMD GPU device node bypass a buffer-count bounds check and drive the parser loop far past the end of a message buffer object, producing out-of-bounds kernel reads that crash the system (availability) and can disclose kernel memory (confidentiality). Exploitation is not remote or unauthenticated: the attacker must be a local principal able to submit VCN decode messages and must additionally allocate a roughly 4 GiB GPU-accessible mapping so msg[1] passes the earlier 'header does not fit in BO' check, a substantial resource precondition that our assessment scores as high attack complexity (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H). …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Requires LOCAL access to an AMD GPU device node (render/DRI) on a kernel with the amdgpu driver and VCN (Video Core Next) decode support - i.e., an authenticated local user able to submit VCN decode messages (PR:L). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | This is a genuine but modest-priority local vulnerability. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Vendor-released patches are available: upgrade to Linux 6.1.188, 6.6.157, 6.12.110, 6.18.51, 7.2.5, or 7.3-rc1 (whichever matches your branch), applying the stable-tree fixes referenced at https://git.kernel.org/stable/c/6dceaeceaa7c8396339f3ea34b0110cb912ca61b, https://git.kernel.org/stable/c/4d7390530853eb7befda9cc786e4c86e8ad7ac9e, https://git.kernel.org/stable/c/9ae19bd60891bea0a7b7504cc8dbfe74570ac3b3, https://git.kernel.org/stable/c/47799e1f893d47d8af231710a61065e3ec8a13e8, https://git.kernel.org/stable/c/7e28853c78c20bb8ba4c1dba702430cd05e09f76 and https://git.kernel.org/stable/c/c2340281be4ddacb8c203e2bce59b126d1d6c4c8, with the CVE record at https://nvd.nist.gov/vuln/detail/CVE-2026-89818; since the flaw is entirely local and GPU-path specific, patching is a straightforward kernel update on affected hosts. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory all Linux systems with AMD GPUs (workstations, servers, cloud instances, GPU passthrough VMs, and containers) and audit permissions on AMD GPU device nodes to ensure only trusted local users can submit VCN decode messages. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
On BIG-IP versions 16.0.x before 16.0.1.1, 15.1.x before 15.1.2.1, 14.1.x before 14.1.4, 13.1.x before 13.1.3.6, and 12.
An exploitable code execution vulnerability exists in the Shader functionality of AMD Radeon DirectX 11 Driver atidxx64.
An exploitable code execution vulnerability exists in the Shader functionality of AMD Radeon DirectX 11 Driver atidxx64.
An exploitable code execution vulnerability exists in the Shader functionality of AMD Radeon DirectX 11 Driver atidxx64.
An exploitable memory corruption vulnerability exists in AMD atidxx64.dll 26.20.15019.19000 graphics driver. Rated criti
plays_service.exe in the plays.tv service before 1.27.7.0, as distributed in AMD driver-installation packages and Gaming
A flaw was found in the KVM's AMD code for supporting SVM nested virtualization. Rated high severity (CVSS 8.8), this vu
AMD ATI atillk64.sys 5.11.9.0 allows low-privileged users to interact directly with physical memory by calling one of se
An exploitable out-of-bounds read vulnerability exists in AMD ATIDXX64.DLL driver, version 26.20.13001.29010. Rated high
AMD fglrx-driver before 15.9 allows local users to gain privileges via a symlink attack. Rated high severity (CVSS 7.8),
AMD fglrx-driver before 15.7 allows local users to gain privileges via a symlink attack. Rated high severity (CVSS 7.8),
A vulnerability, which was classified as critical, has been found in TechPowerUp Ryzen DRAM Calculator 1.2.0.5.sys. Rate
Same technique Buffer Overflow
View allShare
External POC / Exploit Code
Leaving vuln.today