Process hangs via stale engine initialization state
Published Nov 20, 2026 · Updated Nov 20, 2026
Initialization failure in Linux Nouveau allows local users to hang or crash decoding processes through VA-API requests. The nvkm_subdev_init_() function leaves use.enabled set after initialization fails, so a subsequent reference skips initialization and submits work to an engine without microcode. On Kepler GPUs missing video decoder firmware, local access to hardware decoding leads to stalled fence waits or process termination with SIGBUS.
Summary
What happened
Initialization failure in Linux Nouveau allows local users to hang or crash decoding processes through VA-API requests. The nvkm_subdev_init_() function leaves use.enabled set after initialization fails, so a subsequent reference skips initialization and submits work to an engine without microcode. On Kepler GPUs missing video decoder firmware, local access to hardware decoding leads to stalled fence waits or process termination with SIGBUS.
The record
- CVE
- CVE-2026-99614
- Published
- Nov 20, 2026
- Updated
- Nov 20, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 20, 2026CVE publishedPublication date reported by the CVE source.
- Nov 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.2
- Affected versionversion=8478cd5a740a092163c8ad5b6da1a1b488eb42bd <58899bfd5cf688733c909adb6aa34929c44c8842
- Affected versionversion=8478cd5a740a092163c8ad5b6da1a1b488eb42bd <765b4f3fe5003b91d8ad8a47a4d3f62dba5d9e3d
- Affected versionversion=8478cd5a740a092163c8ad5b6da1a1b488eb42bd <8d642da3ec15d0c169948c0af60c6e94cf31a539
- Affected versionversion=8478cd5a740a092163c8ad5b6da1a1b488eb42bd <a1f7f37417bacf2eaf80a8ce6b598b1fa56f8906
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us