CVE-2026-99773 (GCVE-0-2026-99773)
Vulnerability from cvelistv5 – Published: 2026-11-20 05:51 – Updated: 2026-11-20 05:51| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
6d6003c4b613c93973e4e870d83f4bed2ad9ac34 , < dd9a96b2271e28340acf2e3764914fe5f32f6102
(git)
Affected: 6d6003c4b613c93973e4e870d83f4bed2ad9ac34 , < 07b2d7a3f2b984c20f5f2630a94f43ede387a8dc (git) Affected: 6d6003c4b613c93973e4e870d83f4bed2ad9ac34 , < f8e6f4deb868fd9da3eda95db222609ab1edc18d (git) Affected: 6d6003c4b613c93973e4e870d83f4bed2ad9ac34 , < 3be436cbd3d265fe4fcfbb5b650edad7b2108443 (git) |
guessed | |
| Linux | Linux |
Affected:
4.10
Unaffected: 0 , < 4.10 (semver) Unaffected: 6.12.118 , ≤ 6.12.* (semver) Unaffected: 6.18.64 , ≤ 6.18.* (semver) Unaffected: 7.3.5 , ≤ 7.3.* (semver) Unaffected: 7.4-rc2 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/drm_crtc.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "dd9a96b2271e28340acf2e3764914fe5f32f6102",
"status": "affected",
"version": "6d6003c4b613c93973e4e870d83f4bed2ad9ac34",
"versionType": "git"
},
{
"lessThan": "07b2d7a3f2b984c20f5f2630a94f43ede387a8dc",
"status": "affected",
"version": "6d6003c4b613c93973e4e870d83f4bed2ad9ac34",
"versionType": "git"
},
{
"lessThan": "f8e6f4deb868fd9da3eda95db222609ab1edc18d",
"status": "affected",
"version": "6d6003c4b613c93973e4e870d83f4bed2ad9ac34",
"versionType": "git"
},
{
"lessThan": "3be436cbd3d265fe4fcfbb5b650edad7b2108443",
"status": "affected",
"version": "6d6003c4b613c93973e4e870d83f4bed2ad9ac34",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/drm_crtc.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "4.10"
},
{
"lessThan": "4.10",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.118",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.64",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc2",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.118",
"versionStartIncluding": "4.10",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.64",
"versionStartIncluding": "4.10",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.5",
"versionStartIncluding": "4.10",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc2",
"versionStartIncluding": "4.10",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/drm_crtc: ensure dma_fence_ops remain valid during device unbind\n\nIn [1], sashiko reported the following issue:\n\n=== snip ===\nLooking at how these fences are managed, drm_crtc_create_fence()\ncreates a dma_fence without taking a reference to the drm_device or\ndrm_crtc. Because the sync_file framework exposes this fence to\nuserspace, the fence can outlive the CRTC.\n\nThe dma_fence contract requires that data accessed by dma_fence_ops\n(like get_driver_name) must remain valid for an RCU grace period after\nthe fence is signaled. However, drm_crtc_cleanup() and the subsequent\nfreeing of the device do not wait for an RCU grace period via\nsynchronize_rcu().\n\nIf userspace calls ioctl(SYNC_IOC_FILE_INFO) concurrently with a device\nhot-unplug:\n\nCPU1 (Userspace)\nsync_file_get_name()\n ops = rcu_dereference(fence-\u003eops);\n if (!dma_fence_test_signaled_flag())\n // Preempted or delayed here\n\nCPU2 (Driver Teardown)\nSignals the fence (setting fence-\u003eops = NULL)\nDestroys and frees the CRTC without waiting for an RCU grace period\n\nCPU1 (Resumes)\n ops-\u003eget_driver_name(fence) -\u003e drm_crtc_fence_get_driver_name()\n crtc = fence_to_crtc(fence); // Casts to the freed CRTC\n return crtc-\u003edev-\u003edriver-\u003ename; // Use-after-free\n\n...\n\nDoes the CRTC or DRM device need to be kept alive for the RCU grace\nperiod, or should the fence hold a proper reference to prevent the\nuse-after-free when get_driver_name() and get_timeline_name() access\nthe freed CRTC structure?\n=== snap ===\n\nI believe this to be a correct observation and this patch implements\nthe suggestion of waiting for an RCU grace period before proceeding\nwith destruction of the drm_crtc, so that get_driver_name() and\nget_timeline_name() can still work."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T05:51:37.923Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/dd9a96b2271e28340acf2e3764914fe5f32f6102"
},
{
"url": "https://git.kernel.org/stable/c/07b2d7a3f2b984c20f5f2630a94f43ede387a8dc"
},
{
"url": "https://git.kernel.org/stable/c/f8e6f4deb868fd9da3eda95db222609ab1edc18d"
},
{
"url": "https://git.kernel.org/stable/c/3be436cbd3d265fe4fcfbb5b650edad7b2108443"
}
],
"title": "drm/drm_crtc: ensure dma_fence_ops remain valid during device unbind",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99773",
"datePublished": "2026-11-20T05:51:37.923Z",
"dateReserved": "2026-09-25T10:25:14.433Z",
"dateUpdated": "2026-11-20T05:51:37.923Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-99773",
"date": "2026-11-20",
"epss": "0.00157",
"percentile": "0.04934"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/drm_crtc.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "dd9a96b2271e28340acf2e3764914fe5f32f6102",
"status": "affected",
"version": "6d6003c4b613c93973e4e870d83f4bed2ad9ac34",
"versionType": "git"
},
{
"lessThan": "07b2d7a3f2b984c20f5f2630a94f43ede387a8dc",
"status": "affected",
"version": "6d6003c4b613c93973e4e870d83f4bed2ad9ac34",
"versionType": "git"
},
{
"lessThan": "f8e6f4deb868fd9da3eda95db222609ab1edc18d",
"status": "affected",
"version": "6d6003c4b613c93973e4e870d83f4bed2ad9ac34",
"versionType": "git"
},
{
"lessThan": "3be436cbd3d265fe4fcfbb5b650edad7b2108443",
"status": "affected",
"version": "6d6003c4b613c93973e4e870d83f4bed2ad9ac34",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/drm_crtc.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "4.10"
},
{
"lessThan": "4.10",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.118",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.64",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc2",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/drm_crtc: ensure dma_fence_ops remain valid during device unbind\n\nIn [1], sashiko reported the following issue:\n\n=== snip ===\nLooking at how these fences are managed, drm_crtc_create_fence()\ncreates a dma_fence without taking a reference to the drm_device or\ndrm_crtc. Because the sync_file framework exposes this fence to\nuserspace, the fence can outlive the CRTC.\n\nThe dma_fence contract requires that data accessed by dma_fence_ops\n(like get_driver_name) must remain valid for an RCU grace period after\nthe fence is signaled. However, drm_crtc_cleanup() and the subsequent\nfreeing of the device do not wait for an RCU grace period via\nsynchronize_rcu().\n\nIf userspace calls ioctl(SYNC_IOC_FILE_INFO) concurrently with a device\nhot-unplug:\n\nCPU1 (Userspace)\nsync_file_get_name()\n ops = rcu_dereference(fence-\u003eops);\n if (!dma_fence_test_signaled_flag())\n // Preempted or delayed here\n\nCPU2 (Driver Teardown)\nSignals the fence (setting fence-\u003eops = NULL)\nDestroys and frees the CRTC without waiting for an RCU grace period\n\nCPU1 (Resumes)\n ops-\u003eget_driver_name(fence) -\u003e drm_crtc_fence_get_driver_name()\n crtc = fence_to_crtc(fence); // Casts to the freed CRTC\n return crtc-\u003edev-\u003edriver-\u003ename; // Use-after-free\n\n...\n\nDoes the CRTC or DRM device need to be kept alive for the RCU grace\nperiod, or should the fence hold a proper reference to prevent the\nuse-after-free when get_driver_name() and get_timeline_name() access\nthe freed CRTC structure?\n=== snap ===\n\nI believe this to be a correct observation and this patch implements\nthe suggestion of waiting for an RCU grace period before proceeding\nwith destruction of the drm_crtc, so that get_driver_name() and\nget_timeline_name() can still work."
}
],
"id": "CVE-2026-99773",
"lastModified": "2026-11-20T06:18:16.143",
"metrics": {},
"published": "2026-11-20T06:18:16.143",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/07b2d7a3f2b984c20f5f2630a94f43ede387a8dc"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/3be436cbd3d265fe4fcfbb5b650edad7b2108443"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/dd9a96b2271e28340acf2e3764914fe5f32f6102"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/f8e6f4deb868fd9da3eda95db222609ab1edc18d"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-20T10:21:32+00:00",
"cve": "CVE-2026-99773",
"id": "CVE-2026-99773",
"initial_release_date": "2026-11-20T05:51:37.923000+00:00",
"product_status:known_affected": "176",
"product_status:known_not_affected": "28",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: Denial of Service via use-after-free during DRM device unbind",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99773.json",
"version": "3"
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.