LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49490: drm/msm/mdp5: Return error code in mdp5_pipe_release when deadlock is detected

In the Linux kernel, the following vulnerability has been resolved: drm/msm/mdp5: Return error code in mdp5_pipe_release when deadlock is detected mdp5_get_global_state runs the risk of hitting a -EDEADLK when acquiring the modeset lock, but currently mdp5_pipe_release doesn't check for if an error is returned. Because of this, there is a possibility of mdp5_pipe_release hitting a NULL dereference error. To avoid this, let's have mdp5_pipe_release check if mdp5_get_global_state returns an error and propogate that error. Changes since v1: - Separated declaration and initialization of *new_state to avoid compiler warning - Fixed some spelling mistakes in commit message Changes since v2: - Return 0 in case where hwpipe is NULL as this is considered normal behavior - Added 2nd patch in series to fix a similar NULL dereference issue in mdp5_mixer_release Patchwork: https://patchwork.freedesktop.org/patch/485179/

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 reliability flaw in the Qualcomm MSM MDP5 display driver. Under a deadlock error path, the driver may miss an error and dereference a NULL value. The public record does not provide CVSS, attacker requirements, or confirmed business impact.

Executive priority

Treat as a targeted kernel maintenance item, not an internet-wide emergency based on current evidence. Prioritize patching where Qualcomm display hardware supports production, kiosk, mobile, or embedded workloads.

Technical view

mdp5_get_global_state can return -EDEADLK while acquiring the modeset lock. mdp5_pipe_release did not check that error before using the returned state, creating a possible NULL dereference. The fix propagates the error instead of continuing on the invalid state.

Likely exposure

Exposure appears limited to Linux kernels using the drm/msm/mdp5 display path, especially Qualcomm MSM/MDP5 environments on affected kernel versions. Generic Linux servers without this driver or hardware path are less likely exposed, but asset validation is required.

Exploitation context

The source bundle does not cite active exploitation, KEV listing, public exploit code, or a remote attack path. It describes a kernel NULL dereference risk triggered through a deadlock/error path in display-driver state handling.

Researcher notes

Evidence is limited to CVE metadata and Linux stable commit references. The record lacks CVSS, CWE, exploitability analysis, and distribution-specific fixed versions. Avoid assuming remote exploitability or privilege escalation without additional vendor evidence.

Mitigation direction

  • Apply vendor-supported kernel updates containing the referenced stable fixes.
  • Prioritize affected Qualcomm MSM/MDP5 systems and embedded Linux images.
  • Check distribution advisories before backporting manually.
  • Avoid unsupported kernel patches without vendor validation.

Validation and detection

  • Inventory kernels and confirm whether drm/msm/mdp5 is present or enabled.
  • Compare deployed kernel versions against vendor fixed packages.
  • Review kernel logs for mdp5 or DRM NULL dereference crashes.
  • Confirm updated builds include the referenced stable commits.
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-49490 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
LinuxLinux7907a0d77cb461f58045763c205a5830be72e97c, 7907a0d77cb461f58045763c205a5830be72e97c, 7907a0d77cb461f58045763c205a5830be72e97c, 7907a0d77cb461f58045763c205a5830be72e97c, 7907a0d77cb461f58045763c205a5830be72e97c, 7907a0d77cb461f58045763c205a5830be72e97c, 7907a0d77cb461f58045763c205a5830be72e97cunaffected
LinuxLinux4.18, 0, 4.19.247, 5.4.198, 5.10.121, 5.15.46, 5.17.14, 5.18.3, 5.19affected
Weakness

CWE details

No CWE listed

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