CVE Professor
›
Back
CVE-2026-99773

CVE-2026-99773 — Linux Linux (dd9a96b2271e28340acf2e3764914fe5f32f6102) — NONE Vulnerability

NONE CVSS 0 NVD+CVE.org

CVE-2026-99773 is a NONE severity security vulnerability (CVSS 0.0/10) affecting Linux Linux (dd9a96b2271e28340acf2e3764914fe5f32f6102). Technical vector analysis shows that an attacker can exploit this flaw remotely over the network without authentication (PR:N) with zero user interaction (UI:N), posing a direct security risk to affected deployments.

📄 Official NVD / MITRE Original Record Text

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.

Published 20.11.2026
ISO Date 2026-11-20
Source NVD+CVE.org
AI Security Analysis & Remediation
🤖 Generating Deep AI Security Analysis…
Analyzing CVSS vector & CWE weakness structure…

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-99773
CVSS 0/10 · UNKNOWN · 20.11.2026
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🎯 WHAT IS THIS VULNERABILITY?
Summary: 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
u…
Affected: Linux:Linux, Linux:Linux

⚡ ATTACK CHAIN
CVSS vector not available. Review vendor advisory.

🌍 REAL WORLD IMPACT

🛡️ REMEDIATION
→ Apply vendor security update for Linux:Linux.
→ Add WAF rule, create IDS alert for anomalous traffic.

⚠️ URGENCY
📌 Low priority — routine update sufficient.

────────────────────────────────────────
[Kural Tabanlı Otomatik Güvenlik Analizi]

Target Reconnaissance Queries (FOFA & Shodan)

FOFA Query

app="Linux Linux"
CVSS Score
0 / 10 · CVSS NONE
Affected Products (2)
Linux:Linux (dd9a96b2271e28340acf2e3764914fe5f32f6102) Linux:Linux (4.10)
Related CVEs
0.0
CVE-2026-126540
Convert::ASN1 versions before 0.37 for Perl allow CPU exhaustion via quadratic bigint loop in os2ip. Every IN
0.0
CVE-2026-126568
Convert::ASN1 versions before 0.37 for Perl allow memory exhaustion via unbounded MSG_PEEK buffer doubling in
0.0
CVE-2026-126576
Convert::ASN1 versions before 0.37 for Perl allow CPU exhaustion via unchecked exponent length in binary REAL
0.0
CVE-2026-126682
Convert::ASN1 versions before 0.37 for Perl allow CPU exhaustion via exponent-notation string in INTEGER encod
0.0
CVE-2026-126819
Convert::ASN1 versions before 0.37 for Perl allow memory exhaustion via zero-length BIT STRING content. A BIT
0.0
CVE-2026-126956
Convert::ASN1 versions before 0.37 for Perl allow memory exhaustion via unlimited recursion depth in construct