EUVD-2026-45763

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: check numentries in GEMOP GETMAPPINGINFO kvcallocargs-numentries, sizeofvmentries, GFPKERNEL at amdgpugem.c:1050 uses the user-supplied numentries directly without any upper bounds check. Since numentries is a u32 and...

CVE-2026-63863

The CVE-2026-63863 entry concerns the Linux kernel drm/gpusvm subsystem. The issue is a unbalanced unlock of gpusvm notifier_lock detected during drm_gpusvm_scan_mm(), where a path under err_free calls drm_gpusvm_notifier_lock() after unlocking, leading to a bad unlock balance warning. Connected ...

CVE-2026-63847 drm/amdgpu/jpeg: set no_user_fence for JPEG v2.5 ring

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/jpeg: set nouserfence for JPEG v2.5 ring JPEG rings do not support 64-bit user fence writes, reject CS submissions with user fences. cherry picked from commit 3216a7f4e2642bda5fd14f57586e835ae9202587...

CVE-2026-63844

Linux kernel vulnerability (CVE-2026-63844) affecting the AMDGPU JPEG path: JPEG rings (v4.0.3) do not support 64-bit user fence writes, so submissions using user fences are rejected. The fix enables no_user_fence for the JPEG ring, addressing the issue via a cherry-picked commit. Exploitation de...

CVE-2026-63842

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/jpeg: set nouserfence for JPEG v5.0.0 ring JPEG rings do not support 64-bit user fence writes, reject CS submissions with user fences. cherry picked from commit 0f43893d3cd478fa57836697525b338817c9c23d...

CVE-2026-63843

The CVE-2026-63843 issue affects the Linux kernel, specifically the drm/amdgpu/jpeg path where JPEG v4.0.5 rings did not support 64-bit user fence writes. The underlying vulnerability arises from enabling user fences for these rings, leading to potential issues when submitting command streams. Th...

CVE-2026-63840 drm/amdgpu/jpeg: set no_user_fence for JPEG v5.3.0 ring

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/jpeg: set nouserfence for JPEG v5.3.0 ring JPEG rings do not support 64-bit user fence writes, reject CS submissions with user fences. cherry picked from commit 86ac011ae234c03fb872f4945913391ea1d8862e...

CVE-2026-53377

In the Linux kernel, the following vulnerability has been resolved: drm/msm: always recover the gpu Previously, in case there was no more work to do, recover worker wouldn't trigger recovery and would instead rely on the gpu going to sleep and then resuming when more work is submitted...

CVE-2026-53377

CVE-2026-53377 affects the Linux kernel DRM MSM driver. The GPU recovery path (Recover_worker) could fail to trigger recovery when no new work is submitted, leaving the GPU hung and potentially causing timeouts or unavailability. The fix changes Recover_worker to always recover the GPU (increment...

CVE-2026-53377 drm/msm: always recover the gpu

In the Linux kernel, the following vulnerability has been resolved: drm/msm: always recover the gpu Previously, in case there was no more work to do, recover worker wouldn't trigger recovery and would instead rely on the gpu going to sleep and then resuming when more work is submitted...

EUVD-2026-45450

In the Linux kernel, the following vulnerability has been resolved: drm/msm: always recover the gpu Previously, in case there was no more work to do, recover worker wouldn't trigger recovery and would instead rely on the gpu going to sleep and then resuming when more work is submitted...

CVE-2026-53377

In the Linux kernel, the following vulnerability has been resolved: drm/msm: always recover the gpu Previously, in case there was no more work to do, recover worker wouldn't trigger recovery and would instead rely on the gpu going to sleep and then resuming when more work is submitted...

CVE-2026-53377 drm/msm: always recover the gpu

In the Linux kernel, the following vulnerability has been resolved: drm/msm: always recover the gpu Previously, in case there was no more work to do, recover worker wouldn't trigger recovery and would instead rely on the gpu going to sleep and then resuming when more work is submitted...

CVE-2026-53374

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: zero-initialize GART table on allocation GART TLB is flushed after unmapping but not after mapping. Since amdgpubocreatekernel does not zero-initialize the buffer, when a single PTE is written the TLB may speculativel...

CVE-2026-53374 drm/amdgpu: zero-initialize GART table on allocation

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: zero-initialize GART table on allocation GART TLB is flushed after unmapping but not after mapping. Since amdgpubocreatekernel does not zero-initialize the buffer, when a single PTE is written the TLB may speculativel...

PT-2026-61471

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A reference leak occurs in the a6xx gpu init function within the drm/msm/adreno component. The node variable is obtained via of parse phandle, but certain early error return paths bypass...

PT-2026-61164

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the drm/amdgpu/jpeg component where JPEG v2.5 rings do not support 64-bit user fence writes. A user fence is a synchronization mechanism used to coordinate tasks betwe...

PT-2026-61415

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the drm/virtio component where the functions virtio gpu cursor plane update and virtio gpu resource flush fail to properly handle the return value of virtio gpu array...

PT-2026-61366

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A NULL pointer dereference can be triggered in the adreno get param function when userspace queries UBWC-related parameters on a2xx-a4xx Adreno drivers. This occurs because these hardwar...

Chromium: CVE-2026-15900 Use after free in GPU

This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...