CVE-20XX-?
agent?

CVE-2025-38404

5.5 MEDIUM 0.2% exploit odds Fix listed Other OS & kernel

What it is

In the Linux kernel, the following vulnerability has been resolved: usb: typec: displayport: Fix potential deadlock The deadlock can occur due to a recursive lock acquisition of `cros_typec_altmode_data::mutex`. The call chain is as follows: 1. cros_typec_altmode_work() acquires the mutex 2. typec_altmode_vdm() -> dp_altmode_vdm() -> 3. typec_altmode_exit() -> cros_typec_altmode_exit() 4. cros_typec_altmode_exit() attempts to acquire the mutex again To prevent this, defer the `typec_altmode_exit()` call by scheduling it rather than calling it directly from within the mutex-protected context.

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

  1. PublishedDisclosed publicly on CVE.org and NVD
  2. Last updatedMost recent change to the record

Why it ranks here

Details

Published
Last modified
Exploit probability
0.2% · EPSS, next 30 days
Weakness
CWE-667
Record status
Analyzed

Affected

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-38404.md and follow it. Check whether this project is affected by CVE-2025-38404. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Meme: I wake up, CVE-2025-38404
Download Square Reddit

Fix and advisories

References

NVD record · CVE.org record