GHSA-F9VC-R5F2-M3X9
Vulnerability from github – Published: 2026-10-28 12:31 – Updated: 2026-10-30 15:34In the Linux kernel, the following vulnerability has been resolved:
drm/exec: don't immediately add prelocked obj to array of locked objs
When a contention is detected the drm_exec object grabs a reference to the contended object, unlocks all other objects and pre-locks the contended one before anything else.
The problem is that it is possible that this pre-locked object was about to be destroyed and drm_exec is now holding the last reference to it.
So we never actually see this pre-locked object again to be explicitly locked and so also never reserve a slot for a dma_fence object on it.
Should the driver now use drm_exec_for_each_locked_object() to add a new fence to all locked objects we eventually see a warning or even a BUG_ON() to prevent random memory corruption.
Fix this by keeping the prelocked object out of the array of locked objs until it was explicitly mentioned by the driver again.
If the prelocked object is never mentioned again by the driver just unlock and drop the reference at the end of the locking loop.
{
"affected": [],
"aliases": [
"CVE-2026-99147"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-28T11:17:34Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/exec: don\u0027t immediately add prelocked obj to array of locked objs\n\nWhen a contention is detected the drm_exec object grabs a reference to\nthe contended object, unlocks all other objects and pre-locks the\ncontended one before anything else.\n\nThe problem is that it is possible that this pre-locked object was about\nto be destroyed and drm_exec is now holding the last reference to it.\n\nSo we never actually see this pre-locked object again to be explicitly\nlocked and so also never reserve a slot for a dma_fence object on it.\n\nShould the driver now use drm_exec_for_each_locked_object() to add a new\nfence to all locked objects we eventually see a warning or even a\nBUG_ON() to prevent random memory corruption.\n\nFix this by keeping the prelocked object out of the array of locked objs\nuntil it was explicitly mentioned by the driver again.\n\nIf the prelocked object is never mentioned again by the driver\njust unlock and drop the reference at the end of the locking loop.",
"id": "GHSA-f9vc-r5f2-m3x9",
"modified": "2026-10-30T15:34:23Z",
"published": "2026-10-28T12:31:05Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99147"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/26401a4999f1596a515b2e704e7066ac09306488"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/74b4d2370a9e2b77247063dfa05f452766102676"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7a10cd79c4d9a90334fece32fef3a8e5b1a9727b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/96d9996e5dbcfabed052c0d9377a382c95fed607"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9dd91a22f076a4d19f14d82a5ab790c6bbaa073e"
}
],
"schema_version": "1.4.0",
"severity": []
}
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
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.