CVE-2025-37967
What it is
In the Linux kernel, the following vulnerability has been resolved: usb: typec: ucsi: displayport: Fix deadlock This patch introduces the ucsi_con_mutex_lock / ucsi_con_mutex_unlock functions to the UCSI driver. ucsi_con_mutex_lock ensures the connector mutex is only locked if a connection is established and the partner pointer is valid. This resolves a deadlock scenario where ucsi_displayport_remove_partner holds con->mutex waiting for dp_altmode_work to complete while dp_altmode_work attempts to acquire it.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-667
- Record status
- Analyzed
Affected
- Linux Kernel < 5.15.184
- Linux Kernel < 6.1.140
- Linux Kernel < 6.6.92
- Linux Kernel < 6.12.30
- Linux Kernel < 6.14.7
- Linux Kernel 6.15
- Debian Linux 11.0
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-37967.md and follow it. Check whether this project is affected by CVE-2025-37967. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/364618c89d4c57c85e5fc51a2446cd939bf57802
- https://git.kernel.org/stable/c/5924b324468845fc795bd76f588f51d7ab4f202d
- https://git.kernel.org/stable/c/61fc1a8e1e10cc784cab5829930838aaf1d37af5
- https://git.kernel.org/stable/c/962ce9028ca6eb450d5c205238a3ee27de9d214d
- https://git.kernel.org/stable/c/f32451ca4cb7dc53f2a0e2e66b84d34162747eb7
- https://git.kernel.org/stable/c/f4bd982563c2fd41ec9ca6c517c392d759db801c
References
- https://git.kernel.org/stable/c/364618c89d4c57c85e5fc51a2446cd939bf57802
- https://git.kernel.org/stable/c/5924b324468845fc795bd76f588f51d7ab4f202d
- https://git.kernel.org/stable/c/61fc1a8e1e10cc784cab5829930838aaf1d37af5
- https://git.kernel.org/stable/c/962ce9028ca6eb450d5c205238a3ee27de9d214d
- https://git.kernel.org/stable/c/f32451ca4cb7dc53f2a0e2e66b84d34162747eb7
- https://git.kernel.org/stable/c/f4bd982563c2fd41ec9ca6c517c392d759db801c
- https://lists.debian.org/debian-lts-announce/2025/08/msg00010.html