kernel: drm/amdgpu: Refactor amdgpu_gem_va_ioctl for Handling Last Fence Update and Timeline Management v4

A flaw was found in the Linux kernel's AMD GPU amdgpu driver. Incorrect management of graphics memory dmafence references within the amdgpugemvaioctl function can lead to a reference count underflow and a use-after-after-free condition. A local attacker could exploit this vulnerability to trigger...

kernel: drm/amdgpu: Refactor amdgpu_gem_va_ioctl for Handling Last Fence Update and Timeline Management v4

A flaw was found in the Linux kernel's AMD GPU amdgpu driver. Incorrect management of graphics memory dmafence references within the amdgpugemvaioctl function can lead to a reference count underflow and a use-after-after-free condition. A local attacker could exploit this vulnerability to trigger...

CVE-2026-72388

A flaw was found in the Linux kernel's drm/panthor component. This vulnerability arises from the incorrect acquisition of fence locks, where an IRQ-safe variant was not consistently used for dmafence objects. Since these objects can be accessed from hard interrupt hardirq context by other drivers...

CVE-2026-72388

The CVE-2026-72388 entry concerns the Linux kernel DRM/Panthor driver. Root cause: when acquiring the dma_fence lock, drivers can be reached from hardirq context, requiring the IRQ-safe variant and a guard-model switch. Affected component is drm/panthor in the kernel’s fence handling; fix involve...

CVE-2026-72388 drm/panthor: Always use the IRQ-safe variant when acquiring the fence lock

In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Always use the IRQ-safe variant when acquiring the fence lock Since dmafence objects can be shared with other subsystems, they may be accessed from hardirq context in those drivers, and we have to take that into...

drm/virtio: fix dma_fence refcount leak on error in virtio_gpu_dma_fence_wait()

...

CVE-2026-53190 drm/virtio: fix dma_fence refcount leak on error in virtio_gpu_dma_fence_wait()

In the Linux kernel, the following vulnerability has been resolved: drm/virtio: fix dmafence refcount leak on error in virtiogpudmafencewait dmafenceunwrapforeach internally calls dmafenceunwrapfirst which does cursor-chain = dmafencegethead, taking an extra reference. On normal loop completion,...

CVE-2026-43237

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Refactor amdgpugemvaioctl for Handling Last Fence Update and Timeline Management v4 This commit simplifies the amdgpugemvaioctl function, key updates include: - Moved the logic for managing the last update fence...

EUVD-2022-55086

Malicious code in bioql PyPI...

CVE-2022-49137 drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj

In the Linux kernel, the following vulnerability has been resolved: drm/amd/amdgpu/amdgpucs: fix refcount leak of a dmafence obj This issue takes place in an error path in amdgpucsfencetohandleioctl. When info-in.what falls into default case, the function simply returns -EINVAL, forgetting to...

CVE-2022-49137

CVE-2022-49137 concerns a refcount leak in the Linux kernel’s amdgpu_cs_fence_to_handle_ioctl() path. When info->in.what hits the default case, the function returns -EINVAL without decrementing the previously bumped dma_fence refcount, causing leaks. The issue arises from a missing refcount de...

CVE-2024-57920

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority...

GSD-2022-1001084 drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj

drm/amd/amdgpu/amdgpucs: fix refcount leak of a dmafence obj This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven. This ID is fixed in Linux Kernel version v5.17.3 by commit...