CVE-2022-49488: drm/msm/mdp5: Return error code in mdp5_mixer_release when deadlock is detected
In the Linux kernel, the following vulnerability has been resolved:
drm/msm/mdp5: Return error code in mdp5_mixer_release when deadlock is detected
There is a possibility for mdp5_get_global_state to return
-EDEADLK when acquiring the modeset lock, but currently global_state in
mdp5_mixer_release doesn't check for if an error is returned.
To avoid a NULL dereference error, let's have mdp5_mixer_release
check if an error is returned and propagate that error.
Patchwork: https://patchwork.freedesktop.org/patch/485181/
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is an error-handling bug in the drm/msm/mdp5 display driver path. When a lock acquisition returns a deadlock error, the caller can mishandle it and hit a NULL dereference. The public sources do not provide CVSS, CWE, confirmed exploitation, or a business-impact rating.
Executive priority
Handle through normal kernel vulnerability management unless affected assets are confirmed in important production or embedded environments. Urgency is constrained by missing severity data and no known exploitation signal in the provided sources.
Technical view
mdp5_get_global_state can return -EDEADLK while acquiring the modeset lock. mdp5_mixer_release did not check that error before using global_state, creating a possible NULL dereference. The fix checks for the error and propagates it. Affected Linux versions are listed in the CVE source bundle, with multiple stable kernel commit references.
Likely exposure
Exposure is most likely on Linux systems using affected kernel versions and the drm/msm/mdp5 code path. The source bundle lists affected versions from 4.18 through 5.19 ranges, but does not identify distributions, device models, or default configuration exposure.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of active exploitation or public weaponization. The issue appears to be a kernel error-handling flaw leading to NULL dereference risk, not a documented remote exploitation chain.
Researcher notes
The key research point is error propagation from mdp5_get_global_state into mdp5_mixer_release when -EDEADLK occurs during modeset locking. Public metadata is thin: no CVSS, CWE, distribution advisories, exploitability analysis, or named workaround is provided.
Mitigation direction
Apply vendor or distribution kernel updates containing the referenced stable fixes.
Check kernel vendor advisories before assuming upstream version numbers map directly to packages.
Prioritize systems matching affected Linux versions and using the drm/msm/mdp5 driver path.
If patching is delayed, follow vendor guidance; no separate mitigation is named in sources.
Validation and detection
Inventory Linux kernel versions against the affected ranges in the CVE source bundle.
Confirm whether deployed kernels include one of the referenced stable fix commits or backports.
Review vendor package changelogs for CVE-2022-49488 coverage.
Check whether drm/msm/mdp5 is relevant to the deployed kernel and hardware profile.
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-49488 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 26, 2025, 02:13 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.