7730 matches found
CVE-2026-63881
In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: fix a vulnerability of integer overflow in kfd debugger getqueueids computes arraysize = numqueues sizeofuint32t, which could overflow on 32-bit sizet build. using arraysize instead, it saturates to SIZEMAX on overflo...
CVE-2026-63881
CVE-2026-63881 affects the Linux kernel DRM/AMDKFD debugger path. The get_queue_ids() function computed array_size as num_queues * sizeof(uint32_t), which could overflow on 32-bit size_t builds. The fix replaces this with a safe-sized approach using array_size(), causing saturation to SIZE_MAX on...
CVE-2026-63881 drm/amdkfd: fix a vulnerability of integer overflow in kfd debugger
In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: fix a vulnerability of integer overflow in kfd debugger getqueueids computes arraysize = numqueues sizeofuint32t, which could overflow on 32-bit sizet build. using arraysize instead, it saturates to SIZEMAX on overflo...
CVE-2026-63880 drm/amdgpu: fix lock leak on ENOMEM in AMDGPU_GEM_OP_GET_MAPPING_INFO
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix lock leak on ENOMEM in AMDGPUGEMOPGETMAPPINGINFO The AMDGPUGEMOPGETMAPPINGINFO branch of amdgpugemopioctl holds three cleanup-tracked resources before calling kvcalloc: the drmgemobject reference from...
CVE-2026-63880
CVE-2026-63880 affects the Linux kernel AMDGPU driver (drm/amdgpu) in the AMDGPU_GEM_OP_GET_MAPPING_INFO path. A -ENOMEM failure in kvcalloc could skip cleanup and leak three locks (drm_gem_object reference, drm_exec lock on the GEM, and drm_exec lock on the per-process VM root PD), causing a loa...
CVE-2026-63863 drm/gpusvm: Fix unbalanced unlock in drm_gpusvm_scan_mm()
In the Linux kernel, the following vulnerability has been resolved: drm/gpusvm: Fix unbalanced unlock in drmgpusvmscanmm There is a unbalanced lock/unlock to gpusvm notifier lock: 931.045868 ===================================== 931.046509 WARNING: bad unlock balance detected! 931.047149...
EUVD-2026-45547
In the Linux kernel, the following vulnerability has been resolved: drm/gpusvm: Fix unbalanced unlock in drmgpusvmscanmm There is a unbalanced lock/unlock to gpusvm notifier lock: 931.045868 ===================================== 931.046509 WARNING: bad unlock balance detected! 931.047149...
CVE-2026-63852
Summary: The CVE-2026-63852 entry relates to the Linux kernel DRM/AMDGPU VCN engine. The vulnerability arises because VCN encoder and decoder rings do not support 64-bit user fence writes, leading to rejected CS submissions when user fences are used. The root cause is identified as the change to ...
CVE-2026-63846
Summary: CVE-2026-63846 concerns the Linux kernel DRM/amdgpu JPEG v3.0 ring. The issue is that JPEG rings do not support 64-bit user fence writes, so submissions using user fences were rejected, which is the root cause described as a patch in the kernel commit (cherry picked from commit 4d7d774f1...
CVE-2026-63845
The CVE-2026-63845 entry concerns the Linux kernel DRM/AMDGPU JPEG driver: JPEG v4.0 rings do not support 64-bit user fence writes, and submissions using user fences are rejected. This is a local, low-privilege path (LOCAL, LOW attack complexity, user interaction NONE) with high impact on confide...
CVE-2026-63844 drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.3 ring
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/jpeg: set nouserfence for JPEG v4.0.3 ring JPEG rings do not support 64-bit user fence writes, reject CS submissions with user fences. cherry picked from commit 2f6afc97d259d530f4f86c7743efbc573a8da927...
CVE-2026-63842 drm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.0 ring
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-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-53375
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vce: Prevent partial address patches In the case that only one of lo/hi is valid, the patching could result in a bad address written to in FW...
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-53378
In the Linux kernel, the following vulnerability has been resolved: drm/colorop: Fix blob property reference tracking in state lifecycle The colorop state blob property handling had memory leaks during state duplication, destruction, and reset operations. The implementation failed to follow the...
EUVD-2026-45451
In the Linux kernel, the following vulnerability has been resolved: drm/colorop: Fix blob property reference tracking in state lifecycle The colorop state blob property handling had memory leaks during state duplication, destruction, and reset operations. The implementation failed to follow the...
CVE-2026-53378
Summary: CVE-2026-53378 affects the Linux kernel DRM colorop path. The issue is memory leaks in blob property handling during state lifecycle (duplication, destruction, reset) due to not releasing blob references and improper destruction of old state. What’s affected: drm/colorop code in the Linu...
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-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...