CVE-2025-37847

Accelerator hang via recursive cleanup locking

Published May 9, 2025 · Updated May 11, 2026

Improper locking in the Linux kernel IVPU driver allows local users to hang the accelerator during a failed runtime resume. After file_priv->ms_lock is acquired, a resume failure triggers a cold boot path that invokes ivpu_ms_cleanup_all() and re-enters ivpu_ms_cleanup(), which attempts to acquire the same lock. The condition requires local low-privileged access and IVPU hardware; the resulting deadlock interrupts accelerator service without reported data exposure or modification.

CVSS severity5.5
Medium
EPSS probability0.20%
Next 30 days · Sep 16, 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.

Book a demo

Summary

What happened

Improper locking in the Linux kernel IVPU driver allows local users to hang the accelerator during a failed runtime resume. After file_priv->ms_lock is acquired, a resume failure triggers a cold boot path that invokes ivpu_ms_cleanup_all() and re-enters ivpu_ms_cleanup(), which attempts to acquire the same lock. The condition requires local low-privileged access and IVPU hardware; the resulting deadlock interrupts accelerator service without reported data exposure or modification.

The record

CVE
CVE-2025-37847
Published
May 9, 2025
Updated
May 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-667, T1499.004
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. May 9, 2025CVE publishedPublication date reported by the CVE source.
  2. May 11, 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=6.11
  2. Affected versionversion=cdfad4db7756563db7d458216d9e3c2651dddc7d <019634f27a16796eab749e8107dae32099945f29
  3. Affected versionversion=cdfad4db7756563db7d458216d9e3c2651dddc7d <7d12a7d43c7bab9097ba466581d8db702e7908dc
  4. Affected versionversion=cdfad4db7756563db7d458216d9e3c2651dddc7d <9a6f56762d23a1f3af15e67901493c927caaf882
  5. Affected versionversion=cdfad4db7756563db7d458216d9e3c2651dddc7d <f996ecc789b5dbaaf38b6ec0a1917821789cbd9c

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=6.11; version=cdfad4db7756563db7d458216d9e3c2651dddc7d <019634f27a16796eab749e8107dae32099945f29; version=cdfad4db7756563db7d458216d9e3c2651dddc7d <7d12a7d43c7bab9097ba466581d8db702e7908dc; version=cdfad4db7756563db7d458216d9e3c2651dddc7d <9a6f56762d23a1f3af15e67901493c927caaf882; version=cdfad4db7756563db7d458216d9e3c2651dddc7d <f996ecc789b5dbaaf38b6ec0a1917821789cbd9c

Published CVSS scores

5.5NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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.

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

No observations available

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

Weakness, pattern, technique

CWE-667Improper Locking
T1499.004Application or System Exploitation

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

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo