CVE-2026-99773
drm/drm_crtc: ensure dma_fence_ops remain valid during device unbind
No exploitation reported by the sources we read.
- Published2026-11-20
- Fixed in7.3.5 · 6.18.64 · 6.12.118
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
In the Linux kernel, the following vulnerability has been resolved: drm/drm_crtc: ensure dma_fence_ops remain valid during device unbind In [1], sashiko reported the following issue: === snip === Looking at how these fences are managed, drm_crtc_create_fence() creates a dma_fence without taking a reference to the drm_device or drm_crtc. Because the sync_file framework exposes this fence to userspace, the fence can outlive the CRTC. The dma_fence contract requires that data accessed by dma_fence_ops (like get_driver_name) must remain valid for an RCU grace period after the fence is signaled. However, drm_crtc_cleanup() and the subsequent freeing of the device do not wait for an RCU grace period via synchronize_rcu(). If userspace calls ioctl(SYNC_IOC_FILE_INFO) concurrently with a device hot-unplug: CPU1 (Userspace) sync_file_get_name() ops = rcu_dereference(fence->ops); if (!dma_fence_test_signaled_flag()) // Preempted or delayed here CPU2 (Driver Teardown) Signals the fence (setting fence->ops = NULL) Destroys and frees the CRTC without waiting for an RCU grace period CPU1 (Resumes) ops->get_driver_name(fence) -> drm_crtc_fence_get_driver_name() crtc = fence_to_crtc(fence); // Casts to the freed CRTC return crtc->dev->driver->name; // Use-after-free ... Does the CRTC or DRM device need to be kept alive for the RCU grace period, or should the fence hold a proper reference to prevent the use-after-free when get_driver_name() and get_timeline_name() access the freed CRTC structure? === snap === I believe this to be a correct observation and this patch implements the suggestion of waiting for an RCU grace period before proceeding with destruction of the drm_crtc, so that get_driver_name() and get_timeline_name() can still work.
Timeline
dates in UTC- 2026-11-2005:51CVE publishedCNA
Versions per branch
OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.3 | ≥ 6.19.0, < 7.3.5 | 7.3.5 | OSV |
| 6.x | ≥ 6.13.0, < 6.18.64 | 6.18.64 | OSV |
| 6.12 | ≥ 4.10.0, < 6.12.118 | 6.12.118 | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA2 products
As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- Linuxother versions: not affected
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected- ≥ 6d6003c4b613c93973e4e870d83f4bed2ad9ac34, < dd9a96b2271e28340acf2e3764914fe5f32f6102fixed in dd9a96b2271e28340acf2e3764914fe5f32f6102git
- ≥ 6d6003c4b613c93973e4e870d83f4bed2ad9ac34, < 07b2d7a3f2b984c20f5f2630a94f43ede387a8dcfixed in 07b2d7a3f2b984c20f5f2630a94f43ede387a8dcgit
- ≥ 6d6003c4b613c93973e4e870d83f4bed2ad9ac34, < f8e6f4deb868fd9da3eda95db222609ab1edc18dfixed in f8e6f4deb868fd9da3eda95db222609ab1edc18dgit
- ≥ 6d6003c4b613c93973e4e870d83f4bed2ad9ac34, < 3be436cbd3d265fe4fcfbb5b650edad7b2108443fixed in 3be436cbd3d265fe4fcfbb5b650edad7b2108443git
- Linuxother versions: affected
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected- = 4.10no fix stated
Not affected < 4.10 · ≥ 6.12.118, ≤ 6.12.* · ≥ 6.18.64, ≤ 6.18.* · ≥ 7.3.5, ≤ 7.3.* · ≥ 7.4-rc2
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE terms of useCVE recordupdated 2026-11-20
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- kernelAzure Linux:3all versions · no fixed version listed
- linuxDebian:14all versions · no fixed version listed
- linuxDebian:13all versions · fixed in 6.12.118-1
- linuxDebian:12all versions · no fixed version listed
- linux-ltsAlpaquita:streamfrom 6.18.62-r0 · fixed in 6.18.64-r0
- linux-ltsAlpaquita:25from 6.12.115-r0 · no fixed version listed
- linux-ltsAlpaquita:23from 6.1.191-r1 · no fixed version listed
Vendor advisories
kernel: kernel: Denial of Service via use-after-free during DRM device unbind
kernel.src as a component of Red Hat Enterprise Linux 10 · kernel as a component of Red Hat Enterprise Linux 6 · kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6 · +173 more
Fix
- Update Linux kernel to 7.3.5 · 6.18.64 · 6.12.118
- No fix available, says the vendor Red Hat Product Security CVE-2026-99773 · 176 productsAffected
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-11-22
- CNACVSS 3.17.82026-11-22
- FIRST EPSSEPSS score0.2 %2026-11-21
- OSVaffected packages—
- GitHub Advisoriesadvisory—
Identifiers
- AZL-115690same flawAzure Linux · MIT
- EUVD-2026-130890same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-378q-gq2q-w9vqsame flawGitHub Advisory Database · CC-BY-4.0
- DSA-6652-1advisory covering several CVEsDebian · LicenseRef-unstated
Technical details
- CVSS v3 vector
- CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2026-11-20
- Last modified
- 2026-11-22
- NVD status
- Received
- GitHub advisory
- GHSA-378q-gq2q-w9vq
Frequently asked questions
What is CVE-2026-99773?
Is CVE-2026-99773 actively exploited?
What is the CVSS score for CVE-2026-99773?
Running Linux kernel? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website checks · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-378q-gq2q-w9vq
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OpenCVE · OpenCVE terms of service · terms restrict redistribution
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- Red Hat Product Security (CSAF and VEX) · CC-BY-4.0