LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50173: drm/msm/mdp5: Fix global state lock backoff

In the Linux kernel, the following vulnerability has been resolved: drm/msm/mdp5: Fix global state lock backoff We need to grab the lock after the early return for !hwpipe case. Otherwise, we could have hit contention yet still returned 0. Fixes an issue that the new CONFIG_DRM_DEBUG_MODESET_LOCK stuff flagged in CI: WARNING: CPU: 0 PID: 282 at drivers/gpu/drm/drm_modeset_lock.c:296 drm_modeset_lock+0xf8/0x154 Modules linked in: CPU: 0 PID: 282 Comm: kms_cursor_lega Tainted: G W 5.19.0-rc2-15930-g875cc8bc536a #1 Hardware name: Qualcomm Technologies, Inc. DB820c (DT) pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : drm_modeset_lock+0xf8/0x154 lr : drm_atomic_get_private_obj_state+0x84/0x170 sp : ffff80000cfab6a0 x29: ffff80000cfab6a0 x28: 0000000000000000 x27: ffff000083bc4d00 x26: 0000000000000038 x25: 0000000000000000 x24: ffff80000957ca58 x23: 0000000000000000 x22: ffff000081ace080 x21: 0000000000000001 x20: ffff000081acec18 x19: ffff80000cfabb80 x18: 0000000000000038 x17: 0000000000000000 x16: 0000000000000000 x15: fffffffffffea0d0 x14: 0000000000000000 x13: 284e4f5f4e524157 x12: 5f534b434f4c5f47 x11: ffff80000a386aa8 x10: 0000000000000029 x9 : ffff80000cfab610 x8 : 0000000000000029 x7 : 0000000000000014 x6 : 0000000000000000 x5 : 0000000000000001 x4 : ffff8000081ad904 x3 : 0000000000000029 x2 : ffff0000801db4c0 x1 : ffff80000cfabb80 x0 : ffff000081aceb58 Call trace: drm_modeset_lock+0xf8/0x154 drm_atomic_get_private_obj_state+0x84/0x170 mdp5_get_global_state+0x54/0x6c mdp5_pipe_release+0x2c/0xd4 mdp5_plane_atomic_check+0x2ec/0x414 drm_atomic_helper_check_planes+0xd8/0x210 drm_atomic_helper_check+0x54/0xb0 ... ---[ end trace 0000000000000000 ]--- drm_modeset_lock attempting to lock a contended lock without backoff: drm_modeset_lock+0x148/0x154 mdp5_get_global_state+0x30/0x6c mdp5_pipe_release+0x2c/0xd4 mdp5_plane_atomic_check+0x290/0x414 drm_atomic_helper_check_planes+0xd8/0x210 drm_atomic_helper_check+0x54/0xb0 drm_atomic_check_only+0x4b0/0x8f4 drm_atomic_commit+0x68/0xe0 Patchwork: https://patchwork.freedesktop.org/patch/492701/

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel display-driver flaw in the Qualcomm MSM MDP5 DRM path. The public record shows a locking bug caught by kernel CI, not a described remote compromise path. Business urgency depends on whether affected Linux builds run this display stack, especially on Qualcomm-based systems.

Executive priority

Handle through normal kernel patch governance unless inventory shows affected Qualcomm/MSM display deployments. There is insufficient evidence for emergency response, but kernel fixes should not be deferred indefinitely where the driver is present.

Technical view

The mdp5 global state path could return success after lock contention without actually taking the required modeset lock in a !hwpipe case. CONFIG_DRM_DEBUG_MODESET_LOCK flagged the issue during CI. The sources provide stable kernel commits but no CVSS, CWE, exploit description, or impact statement beyond the locking failure.

Likely exposure

Exposure appears most relevant to Linux systems using the drm/msm/mdp5 display driver, with the trace showing Qualcomm DB820c hardware. General Linux servers without this driver or hardware path are less likely to be exposed, but version and configuration checks are required.

Exploitation context

The source bundle does not show active exploitation, public exploit code, KEV listing, or a weaponized path. It documents a kernel CI warning and a resolved lock-backoff issue. Treat exploitation likelihood as unproven from the provided evidence.

Researcher notes

Evidence is narrow: the record describes a missed lock acquisition/backoff condition in mdp5 and includes stable commit references. Impact, reachability, privilege requirements, and exploitability are not defined in the supplied sources, so risk scoring remains uncertain.

Mitigation direction

  • Check vendor kernel advisories for CVE-2022-50173 applicability.
  • Update affected Linux kernels to builds carrying the referenced stable commits.
  • Prioritize Qualcomm/MSM display systems and embedded Linux images for review.
  • Track downstream distro or device-vendor kernel backports before deployment.

Validation and detection

  • Inventory kernel versions against the affected version list.
  • Confirm whether drm/msm/mdp5 is built or loaded.
  • Verify the relevant stable commit is present in kernel source or package changelog.
  • Review kernel logs for related DRM modeset lock warnings.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50173 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
8Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux776f5c58bfe16cf322d71eeed3c5dda1eeac7e6b, b2aa2c4efe93e2580d6a8774b04fe2b99756a322, 49dc28b4b2e28ef7564e355c91487996c1cbebd7, 04bef5f1ba8ea6d7c1c8f5f65e0395c62db59cb8, 33dc5aac46e0fad8f5eb193e5906ed0eb6b66ceb, d59be579fa932c46b908f37509f319cbd4ca9a68, d59be579fa932c46b908f37509f319cbd4ca9a68, 19964dfb39bda4d7716a71009488f0668ecbcf52unaffected
LinuxLinux5.19, 0, 4.19.256, 5.4.211, 5.10.137, 5.15.61, 5.18.18, 5.19.2, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.