Skip to main content
VulnerabilityPublished Updated

CVE-2025-37907: Linux kernel · accel/ivpu: Fix locking order in ivpu_job_submit

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-37907· Medium

Not known to be exploited · CVSS 5.5 Medium.

Data as of 13 Nov 2026, 19:21 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 May 2025

  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 13 Nov 2026.

What to do

AI-suggested

Until a fix is available, avoid triggering fault conditions that cause job aborts in the accel/ivpu subsystem or restrict untrusted local user access to vulnerable kernel components to reduce risk.

Description

CVE-2025-37907 is a medium-severity vulnerability in the Linux kernel's accel/ivpu component caused by an inconsistent locking order in the ivpu_job_submit function. This flaw leads to a deadlock during job submission and abort handling when locks are acquired in conflicting sequences by different threads. The issue arises because one thread locks the submitted_jobs lock before the file_priv lock, while another thread locks file_priv before submitted_jobs, causing a circular wait. The vulnerability does not impact confidentiality or integrity but can cause availability disruption due to deadlock.

References

Community reviews

Loading reviews…