GHSA-549V-HQP3-FGWF
Vulnerability from github – Published: 2026-11-20 06:32 – Updated: 2026-11-20 06:32In the Linux kernel, the following vulnerability has been resolved:
drm/nouveau/nvkm: clear use.enabled when subdev init fails
On Kepler boards without the video decode falcon firmware installed (msvld/mspdec/msppp), every other VA-API decode attempt binds to an engine with no ucode loaded. The submitted work never completes, which leads to a context switch timeout, a channel recovery that cannot reset the engine, and eviction waits on fences that never signal. The process ends up stuck in D state, or killed by SIGBUS when it touches a buffer evicted after the wait times out:
msvld: unable to load firmware data msvld: init failed, -19 fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] vo[5444]: channel 14 killed! WARNING: drivers/gpu/drm/nouveau/nvkm/engine/fifo/runl.c:117 at nvkm_runl_rc+0x2a4/0x3b0 [nouveau] [TTM] Buffer eviction failed WARNING: drivers/gpu/drm/nouveau/nouveau_bo.c:1092 at nouveau_bo_move_ntfy.part.0+0x9b/0x100 [nouveau]
Tracing nvkm_subdev_ref() and nvkm_subdev_init_() shows the pattern: a reference taken with enabled=0 runs nvkm_falcon_init(), which returns -ENODEV; the next reference sees enabled=1 and succeeds without running it.
Clear use.enabled when init() fails, so that every later reference retries init and fails cleanly. The other readers of use.enabled are fini() handlers that use it to skip teardown, which they now also do after a failed init().
On a GK107 (Quadro K1100M) without video firmware, playing H.264 with mpv --hwdec=auto: without this patch the GPU channel is killed within a minute and mpv hangs; with it, VA-API decoder creation fails, mpv falls back to software decoding, and no faults are logged.
{
"affected": [],
"aliases": [
"CVE-2026-99614"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-20T06:17:53Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/nouveau/nvkm: clear use.enabled when subdev init fails\n\nOn Kepler boards without the video decode falcon firmware installed\n(msvld/mspdec/msppp), every other VA-API decode attempt binds to an\nengine with no ucode loaded. The submitted work never completes, which\nleads to a context switch timeout, a channel recovery that cannot reset\nthe engine, and eviction waits on fences that never signal. The process\nends up stuck in D state, or killed by SIGBUS when it touches a buffer\nevicted after the wait times out:\n\n msvld: unable to load firmware data\n msvld: init failed, -19\n fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]\n vo[5444]: channel 14 killed!\n WARNING: drivers/gpu/drm/nouveau/nvkm/engine/fifo/runl.c:117 at nvkm_runl_rc+0x2a4/0x3b0 [nouveau]\n [TTM] Buffer eviction failed\n WARNING: drivers/gpu/drm/nouveau/nouveau_bo.c:1092 at nouveau_bo_move_ntfy.part.0+0x9b/0x100 [nouveau]\n\nTracing nvkm_subdev_ref() and nvkm_subdev_init_() shows the pattern:\na reference taken with enabled=0 runs nvkm_falcon_init(), which\nreturns -ENODEV; the next reference sees enabled=1 and succeeds\nwithout running it.\n\nClear use.enabled when init() fails, so that every later reference\nretries init and fails cleanly. The other readers of use.enabled are\nfini() handlers that use it to skip teardown, which they now also do\nafter a failed init().\n\nOn a GK107 (Quadro K1100M) without video firmware, playing H.264 with\nmpv --hwdec=auto: without this patch the GPU channel is killed within a\nminute and mpv hangs; with it, VA-API decoder creation fails, mpv falls\nback to software decoding, and no faults are logged.",
"id": "GHSA-549v-hqp3-fgwf",
"modified": "2026-11-20T06:32:04Z",
"published": "2026-11-20T06:32:04Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99614"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/58899bfd5cf688733c909adb6aa34929c44c8842"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/765b4f3fe5003b91d8ad8a47a4d3f62dba5d9e3d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8d642da3ec15d0c169948c0af60c6e94cf31a539"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a1f7f37417bacf2eaf80a8ce6b598b1fa56f8906"
}
],
"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
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.