cbcvebase.
CVE-2025-40096
published 2025-10-30

CVE-2025-40096: In the Linux kernel, the following vulnerability has been resolved: drm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies When adding…

PriorityP338high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.14%
4.1th percentile
In the Linux kernel, the following vulnerability has been resolved: drm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies When adding dependencies with drm_sched_job_add_dependency(), that function consumes the fence reference both on success and failure, so in the latter case the dma_fence_put() on the error path (xarray failed to expand) is a double free. Interestingly this bug appears to have been present ever since commit ebd5f74255b9 ("drm/sched: Add dependency tracking"), since the code back then looked like this: drm_sched_job_add_implicit_dependencies(): ... for (i = 0; i < fence_count; i++) { ret = drm_sched_job_add_dependency(job, fences[i]); if (ret) break; } for (; i < fence_count; i++) dma_fence_put(fences[i]); Which means for the failing 'i' the dma_fence_put was already a double free. Possibly there were no users at that time, or the test cases were insufficient to hit it. The bug was then only noticed and fixed after commit 9c2ba265352a ("drm/scheduler: use new iterator in drm_sched_job_add_implicit_dependencies v2") landed, with its fixup of commit 4eaf02d6076c ("drm/scheduler: fix drm_sched_job_add_implicit_dependencies"). At that point it was a slightly different flavour of a double free, which commit 963d0b356935 ("drm/scheduler: fix drm_sched_job_add_implicit_dependencies harder") noticed and attempted to fix. But it only moved the double free from happening inside the drm_sched_job_add_dependency(), when releasing the reference not yet obtained, to the caller, when releasing the reference already released by the former in the failure case. As such it is not easy to identify the right target for the fixes tag so lets keep it simple and just continue the chain. While fixing we also improve the comment and explain the reason for taking the reference and not dropping it.

Affected

22 ranges
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.158-1 (bookworm)linux 6.1.158-1 (bookworm)
debianlinux-6.1< linux 6.1.158-1 (bookworm)linux 6.1.158-1 (bookworm)
linuxlinux
linuxlinux>= 963d0b3569354230f6e2c36a286ef270a8901878 < 4c38a63ae12ecc9370a7678077bde2d61aa80e9c4c38a63ae12ecc9370a7678077bde2d61aa80e9c
linuxlinux>= 963d0b3569354230f6e2c36a286ef270a8901878 < 57239762aa90ad768dac055021f27705dae7334457239762aa90ad768dac055021f27705dae73344
linuxlinux>= 963d0b3569354230f6e2c36a286ef270a8901878 < e5e3eb2aff92994ee81ce633f1c4e73bd4b87e11e5e3eb2aff92994ee81ce633f1c4e73bd4b87e11
linuxlinux>= 963d0b3569354230f6e2c36a286ef270a8901878 < fdfb47e85af1e11ec822c82739dde2dd8dff5115fdfb47e85af1e11ec822c82739dde2dd8dff5115
linuxlinux>= 963d0b3569354230f6e2c36a286ef270a8901878 < 5801e65206b065b0b2af032f7f1eef222aa2fd835801e65206b065b0b2af032f7f1eef222aa2fd83
linuxlinux_kernel>= 0 < 6.1.158-16.1.158-1
linuxlinux_kernel>= 0 < 6.12.57-16.12.57-1
linuxlinux_kernel>= 0 < 6.17.6-16.17.6-1
linuxlinux_kernel>= 0 < 6.8.0-106.1066.8.0-106.106
linuxlinux_kernel>= 0 < 6.17.0-14.146.17.0-14.14
linuxlinux_kernel>= 5.16.0 < 6.1.1586.1.158
linuxlinux_kernel>= 6.13.0 < 6.17.56.17.5
linuxlinux_kernel>= 6.2.0 < 6.6.1146.6.114
linuxlinux_kernel>= 6.7.0 < 6.12.556.12.55
msrcazl3_kernel_6.6.104.2-4_on_azure_linux_3.0
msrcazl3_kernel_6.6.112.1-2_on_azure_linux_3.0
ubuntulinux-aws
ubuntulinux-oracle
ubuntulinux-xilinx

CVSS provenance

nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv3.2LOW
vendor_msrc7.8HIGH
vendor_ubuntu7.8HIGH
vendor_redhat7.0MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.