CVE-2025-37907: Linux kernel · accel/ivpu: Fix locking order in ivpu_job_submit
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 13 Nov 2026, 19:21 UTC
Thin evidence
One scorer or noneCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
- nvd.nist.gov/vuln/detail/CVE-2025-37907 (opens in a new tab)
- git.kernel.org/stable/c/079d2622f8c9e0c380149645fff21d35c59ce6ff (opens in a new tab)
- git.kernel.org/stable/c/ab680dc6c78aa035e944ecc8c48a1caab9f39924 (opens in a new tab)
- git.kernel.org/stable/c/b9b70924a272c2d72023306bc56f521c056212ee (opens in a new tab)