In the Linux kernel, the following vulnerability has been resolved: drm/drmcrtc: ensure dmafenceops remain valid during device unbind In…
CVE-2026-99773
In the Linux kernel, the following vulnerability has been resolved: drm/drmcrtc: ensure dmafenceops remain valid during device unbind In [1], sashiko reported the following issue: === snip === Looking at how these fences are managed, drmcrtccreatefence() creates a dmafence without taking a reference to the drmdevice or drmcrtc. Because the syncfile framework exposes this fence to userspace, the fence can outlive the CRTC. The dmafence contract requires that data accessed by dmafenceops (like getdrivername) must remain valid for an RCU grace period after the fence is signaled. However, drmcrtccleanup() and the subsequent freeing of the device do not wait for an RCU grace period via synchronizercu(). If userspace calls ioctl(SYNCIOCFILEINFO) concurrently with a device hot-unplug: CPU1 (Userspace) syncfilegetname() ops = rcudereference(fence->ops); if (!dmafencetestsignaledflag()) // 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->getdrivername(fence) -> drmcrtcfencegetdrivername() crtc = fencetocrtc(fence); // Casts to the freed CRTC return…
Assessment
- CVSS
- Not yet scored
- Severity
- Unscored
- Known exploited
- Not listed in CISA KEV
- Exploit availability
- Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
- Published
- 20 November 2026
- Last updated
- 20 November 2026
- Assigner
- Linux
At the source
References
- https://git.kernel.org/stable/c/dd9a96b2271e28340acf2e3764914fe5f32f6102
- https://git.kernel.org/stable/c/07b2d7a3f2b984c20f5f2630a94f43ede387a8dc
- https://git.kernel.org/stable/c/f8e6f4deb868fd9da3eda95db222609ab1edc18d
- https://git.kernel.org/stable/c/3be436cbd3d265fe4fcfbb5b650edad7b2108443
- https://nvd.nist.gov/vuln/detail/CVE-2026-99773
Community proofs of concept
No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.
Submit a proof of concept
Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.
Query this programmatically
Agents can read this through the MCP endpoint, or over HTTP:
curl https://cve.zerocrew.in/api/cve/CVE-2026-99773