Skip to main content
VulnerabilityPublished

CVE-2026-99614: Linux kernel · drm/nouveau/nvkm: clear use.enabled when subdev init fails

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99614· Medium

Not known to be exploited · fixed in a1f7f37417bacf2eaf80a8ce6b598b1fa56f8906 : update Linux kernel when convenient.

Data as of 20 Nov 2026, 07:34 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in a1f7f37417bacf2eaf80a8ce6b598b1fa56f8906, 58899bfd5cf688733c909adb6aa34929c44c8842, 765b4f3fe5003b91d8ad8a47a4d3f62dba5d9e3d +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to a1f7f37417bacf2eaf80a8ce6b598b1fa56f8906, 58899bfd5cf688733c909adb6aa34929c44c8842, 765b4f3fe5003b91d8ad8a47a4d3f62dba5d9e3d or 8d642da3ec15d0c169948c0af60c6e94cf31a539.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 8478cd5a740a092163c8ad5b6da1a1b488eb42bd, < a1f7f37417bacf2eaf80a8ce6b598b1fa56f8906
Fixed in
  • a1f7f37417bacf2eaf80a8ce6b598b1fa56f8906
LinuxLinuxAffected
  • ≥ 8478cd5a740a092163c8ad5b6da1a1b488eb42bd, < 58899bfd5cf688733c909adb6aa34929c44c8842
Fixed in
  • 58899bfd5cf688733c909adb6aa34929c44c8842
LinuxLinuxAffected
  • ≥ 8478cd5a740a092163c8ad5b6da1a1b488eb42bd, < 765b4f3fe5003b91d8ad8a47a4d3f62dba5d9e3d
Fixed in
  • 765b4f3fe5003b91d8ad8a47a4d3f62dba5d9e3d
LinuxLinuxAffected
  • ≥ 8478cd5a740a092163c8ad5b6da1a1b488eb42bd, < 8d642da3ec15d0c169948c0af60c6e94cf31a539
Fixed in
  • 8d642da3ec15d0c169948c0af60c6e94cf31a539
LinuxLinuxAffected
  • =6.2
Fixed in–

Description

In 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.

References

Community reviews

Loading reviews…