CVE-2022-50173
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-11-28
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 4.19.247 (inc) to 4.19.256 (exc) |
| linux | linux_kernel | From 5.4.198 (inc) to 5.4.211 (exc) |
| linux | linux_kernel | From 5.10.121 (inc) to 5.10.137 (exc) |
| linux | linux_kernel | From 5.15.46 (inc) to 5.15.61 (exc) |
| linux | linux_kernel | From 5.17.14 (inc) to 5.18 (exc) |
| linux | linux_kernel | From 5.18.3 (inc) to 5.18.18 (exc) |
| linux | linux_kernel | From 5.19 (inc) to 5.19.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-667 | The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a flaw in the Linux kernel's drm/msm/mdp5 driver related to locking mechanisms. Specifically, the code failed to properly acquire a global state lock after an early return condition, which could lead to contention issues where the lock is not held correctly even though contention occurs. This was flagged by the CONFIG_DRM_DEBUG_MODESET_LOCK feature, indicating a problem with how the drm_modeset_lock function handles locking under certain conditions.
How can this vulnerability impact me? :
The vulnerability could cause contention on the drm_modeset_lock, potentially leading to race conditions or inconsistent state in the graphics subsystem of the Linux kernel. This might result in instability or unexpected behavior in graphics rendering or display management on affected devices using the msm/mdp5 driver.