CVE-2026-99773: Linux kernel · drm/drm_crtc: ensure dma_fence_ops remain valid during device unbind
Source GCVE Database
Not known to be exploited · fixed in f8e6f4deb868fd9da3eda95db222609ab1edc18d : patch Linux kernel soon.
Data as of 20 Nov 2026, 07:49 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in f8e6f4deb868fd9da3eda95db222609ab1edc18d, dd9a96b2271e28340acf2e3764914fe5f32f6102, 07b2d7a3f2b984c20f5f2630a94f43ede387a8dc +1
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade Linux kernel to f8e6f4deb868fd9da3eda95db222609ab1edc18d, dd9a96b2271e28340acf2e3764914fe5f32f6102, 07b2d7a3f2b984c20f5f2630a94f43ede387a8dc or 3be436cbd3d265fe4fcfbb5b650edad7b2108443.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented that waits for an RCU grace period before destroying the drm_crtc, ensuring dma_fence_ops remain valid during device unbind. Users should apply the official kernel patch that includes this fix. Since this is a kernel-level issue, updating to a patched kernel version is the recommended mitigation.
Description
CVE-2026-99773 is a use-after-free vulnerability in the Linux kernel's Direct Rendering Manager (DRM) subsystem related to dma_fence operations during device unbind. The issue arises because dma_fence objects exposed to userspace can outlive the associated CRTC device, and the kernel did not wait for an RCU grace period before freeing the CRTC. This could lead to userspace accessing freed memory when querying fence driver names concurrently with device hot-unplug. The vulnerability has been addressed by ensuring the kernel waits for an RCU grace period before destroying the drm_crtc, preventing use-after-free conditions.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99773 (opens in a new tab)
- git.kernel.org/stable/c/07b2d7a3f2b984c20f5f2630a94f43ede387a8dc (opens in a new tab)
- git.kernel.org/stable/c/3be436cbd3d265fe4fcfbb5b650edad7b2108443 (opens in a new tab)
- git.kernel.org/stable/c/dd9a96b2271e28340acf2e3764914fe5f32f6102 (opens in a new tab)
- git.kernel.org/stable/c/f8e6f4deb868fd9da3eda95db222609ab1edc18d (opens in a new tab)