Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-40096: drm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 4c38a63ae12ecc9370a7678077bde2d61aa80e9c, 57239762aa90ad768dac055021f27705dae73344, 5801e65206b065b0b2af032f7f1eef222aa2fd83; azl3 kernel 6.6.112.1-2 on Azure Linux 3.0 6.6.117.1-1.

Low priority for now. Upgrade to Linux Linux 4c38a63ae12ecc9370a7678077bde2d61aa80e9c, 57239762aa90ad768dac055021f27705dae73344, 5801e65206b065b0b2af032f7f1eef222aa2fd83; azl3 kernel 6.6.112.1-2 on Azure Linux 3.0 6.6.117.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Oct 30, 2025
Updated
Oct 19, 2026
EPSS
0.1% · 4th percentile
CWE
—

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-40096

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.16affected
    • 963d0b3569354230f6e2c36a286ef270a8901878 and later · before 4c38a63ae12ecc9370a7678077bde2d61aa80e9caffected · git
    • 963d0b3569354230f6e2c36a286ef270a8901878 and later · before 57239762aa90ad768dac055021f27705dae73344affected · git
    • 963d0b3569354230f6e2c36a286ef270a8901878 and later · before e5e3eb2aff92994ee81ce633f1c4e73bd4b87e11affected · git
    • 963d0b3569354230f6e2c36a286ef270a8901878 and later · before fdfb47e85af1e11ec822c82739dde2dd8dff5115affected · git
    • 963d0b3569354230f6e2c36a286ef270a8901878 and later · before 5801e65206b065b0b2af032f7f1eef222aa2fd83affected · git
    • before 5.16not affected · semver
    • 6.1.158 and later · up to and including 6.1.*not affected · semver
    • 6.6.114 and later · up to and including 6.6.*not affected · semver
    • 6.12.55 and later · up to and including 6.12.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-124.39.1.el10_16.12.0-124.39.1.el10_1
AlmaLinux:10kernel-docbefore 6.12.0-124.39.1.el10_16.12.0-124.39.1.el10_1
AlmaLinux:8bpftoolbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.94.1.rt7.435.el8_104.18.0-553.94.1.rt7.435.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.94.1.rt7.435.el8_104.18.0-553.94.1.rt7.435.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.94.1.rt7.435.el8_104.18.0-553.94.1.rt7.435.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.94.1.rt7.435.el8_104.18.0-553.94.1.rt7.435.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.94.1.rt7.435.el8_104.18.0-553.94.1.rt7.435.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.94.1.rt7.435.el8_104.18.0-553.94.1.rt7.435.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.94.1.rt7.435.el8_104.18.0-553.94.1.rt7.435.el8_10

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-40094Oct 30, 2025 · usb: gadget: f_acm: Refactor bind path to use __free()
    31Monitor
  • ← EarlierCVE-2025-40095Oct 30, 2025 · usb: gadget: f_rndis: Refactor bind path to use __free()
    31Monitor
  • Later →CVE-2025-40097Oct 30, 2025 · ALSA: hda: Fix missing pointer check in hda_component_manager_init function
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux4c38a63ae12ecc9370a7678077bde2d61aa80e9cVendor (CNA)
Linux Linux57239762aa90ad768dac055021f27705dae73344Vendor (CNA)
Linux Linux5801e65206b065b0b2af032f7f1eef222aa2fd83Vendor (CNA)
Linux Linuxe5e3eb2aff92994ee81ce633f1c4e73bd4b87e11Vendor (CNA)
Linux Linuxfdfb47e85af1e11ec822c82739dde2dd8dff5115Vendor (CNA)
azl3 kernel 6.6.112.1-2 on Azure Linux 3.06.6.117.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.158-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-553.94.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-553.94.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-553.94.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-553.94.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-553.94.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-553.94.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-553.94.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-modules0:4.18.0-553.94.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-modules-extra0:4.18.0-553.94.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-devel0:4.18.0-553.94.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-doc0:4.18.0-553.94.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)

+3

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records