usb: typec: displayport: Fix potential deadlock
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.1.144, 6.6.97, 6.12.37, 6.15.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
From 6.1.143 · fixed in 6.1.144; From 6.6.96 · fixed in 6.6.97; From 6.12.36 · fixed in 6.12.37; From 6.15.5 · fixed in 6.15.6
References 8
git.kernel.org
- stable/c/749d9076735fb497aae60fbea9fff563f9ea3254
- stable/c/eb08fca56f1f39e4038cb9bac9864464b13b00aa
- stable/c/7be0d1ea71f52595499da39cea484a895e8ed042
- stable/c/76cf1f33e7319fe74c94ac92f9814094ee8cc84b
- stable/c/63cff9f57e86b2dc25d7487ca0118df89a665296
- stable/c/c782f98eef14197affa8a7b91e6981420f109ea9
- stable/c/80c25d7916a44715338d4f8924c8e52af50d0b9f
- stable/c/099cf1fbb8afc3771f408109f62bdec66f85160e