Local denial of service via lock mishandling
Published Jun 18, 2025 · Updated May 23, 2026
Improper locking in the Linux mdp5 DRM driver allows local users to interrupt service during atomic display updates. mdp5_pipe_release calls mdp5_get_global_state before checking for a null hardware pipe, so lock contention can be recorded even when the function returns success. Reachability requires a local low-privileged user, an affected kernel, and Qualcomm MDP5 display hardware; the documented consequence is loss of availability.
Summary
What happened
Improper locking in the Linux mdp5 DRM driver allows local users to interrupt service during atomic display updates. mdp5_pipe_release calls mdp5_get_global_state before checking for a null hardware pipe, so lock contention can be recorded even when the function returns success. Reachability requires a local low-privileged user, an affected kernel, and Qualcomm MDP5 display hardware; the documented consequence is loss of availability.
The record
- CVE
- CVE-2022-50173
- Published
- Jun 18, 2025
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=04bef5f1ba8ea6d7c1c8f5f65e0395c62db59cb8 <f4e3a8c7e890049e7ba2b49ad0315dae841dfa55
- Affected versionversion=19964dfb39bda4d7716a71009488f0668ecbcf52
- Affected versionversion=33dc5aac46e0fad8f5eb193e5906ed0eb6b66ceb <2fdf5a54ef9376ff69149a48c5616f1141008c9f
- Affected versionversion=4.19.247 <4.19.256
- Affected versionversion=49dc28b4b2e28ef7564e355c91487996c1cbebd7 <bf386c955f35a0a01bef482b6035d40ff2f6cc75
- Affected versionversion=5.10.121 <5.10.137
- Affected versionversion=5.15.46 <5.15.61
- Affected versionversion=5.17.14 <5.18
- Affected versionversion=5.18.3 <5.18.18
- Affected versionversion=5.19
- Affected versionversion=5.4.198 <5.4.211
- Affected versionversion=776f5c58bfe16cf322d71eeed3c5dda1eeac7e6b <247f2934324f9a18d18df24ea4bfcc7d4631d0ef
- Affected versionversion=b2aa2c4efe93e2580d6a8774b04fe2b99756a322 <2e34d6c8180a398de6448a93df25068bf3062042
- Affected versionversion=d59be579fa932c46b908f37509f319cbd4ca9a68 <0b07f28c23ff50a7fa5dbc3f6b3b6bd53ac9fc70
- Affected versionversion=d59be579fa932c46b908f37509f319cbd4ca9a68 <92ef86ab513593c6329d04146e61f9a670e72fc5
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo