CVE-2026-97514

Kernel hang via sleeping control update under spinlock

Published Sep 24, 2026 · Updated Sep 24, 2026

Locking error in the Linux Wave5 VPU decoder 6.12 before 6.12.111 and 6.18 before 6.18.53 allows local users to hang or crash the kernel. Dynamic-resolution handling calls the sleep-capable v4l2_ctrl_find and v4l2_ctrl_s_ctrl operations while state_spinlock is held instead of deferring the control update until after unlock. Triggering requires local access to a compatible Wave5 V4L2 decoder and a decode operation that reaches dynamic-resolution handling.

CVSS severityUnavailable
Unscored
EPSS probability0.15%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Locking error in the Linux Wave5 VPU decoder 6.12 before 6.12.111 and 6.18 before 6.18.53 allows local users to hang or crash the kernel. Dynamic-resolution handling calls the sleep-capable v4l2_ctrl_find and v4l2_ctrl_s_ctrl operations while state_spinlock is held instead of deferring the control update until after unlock. Triggering requires local access to a compatible Wave5 V4L2 decoder and a decode operation that reaches dynamic-resolution handling.

The record

CVE
CVE-2026-97514
Published
Sep 24, 2026
Updated
Sep 24, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Sep 24, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 24, 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.

  1. Affected versionversion=0 <6.12.111
  2. Affected versionversion=0 <6.18.53
  3. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <072beef6a19f9c84dc5a50c5499663a5734c1096
  4. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <629a937091ecf9c5c9f7a18f41cb0e6c778a7b2f
  5. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7d5d364f8b2dcc9b6b92456fb55632fde4a4d96f

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=0 <6.12.111; version=0 <6.18.53; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <072beef6a19f9c84dc5a50c5499663a5734c1096; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <629a937091ecf9c5c9f7a18f41cb0e6c778a7b2f; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7d5d364f8b2dcc9b6b92456fb55632fde4a4d96f

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499Endpoint Denial of Service

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.

Get started