PT-2026-152499
CVE-2026-99619
·
Published
2026-11-20
·
Updated
2026-11-20
Description by
Score
N/A
Not availableNo severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: don't drop the gang dependency fence twice
drm sched job add dependency() drops the fence reference when it fails,
but amdgpu cs submit() drops it again, so the scheduled fence of a gang
member loses a reference it still needs.
A GFX+COMPUTE gang waiting for another context, with the
xarray node allocation for the leader's dependency failed through
failslab:
WARNING: drivers/dma-buf/dma-fence.c:589 at dma fence release+0x34d/0x730, CPU#1: amd uapi regres/2993
drm sched job cleanup+0x2c2/0x340 [gpu sched]
amdgpu job free+0xcb/0x3e0 [amdgpu]
amdgpu cs parser fini+0x435/0x710 [amdgpu]
amdgpu cs ioctl+0xcd2/0x7a60 [amdgpu]
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] SMP KASAN NOPTI
KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]
RIP: 0010:dma fence signal timestamp locked+0x1b8/0x610
(cherry picked from commit 5aa070a83c8378810b906cc8bfc650ce69822a7c)
Found an issue in the description? Have something to add? Feel free to write us 👾