LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48756: drm/msm/dsi: invalid parameter check in msm_dsi_phy_enable

In the Linux kernel, the following vulnerability has been resolved: drm/msm/dsi: invalid parameter check in msm_dsi_phy_enable The function performs a check on the "phy" input parameter, however, it is used before the check. Initialize the "dev" variable after the sanity check to avoid a possible NULL pointer dereference. Addresses-Coverity-ID: 1493860 ("Null pointer dereference")

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-48756 is a Linux kernel bug in the Qualcomm MSM DSI display driver. The code used an input pointer before checking whether it was valid, creating a possible NULL pointer dereference. The public record does not provide CVSS, confirmed impact, or active exploitation evidence.

Executive priority

Treat this as targeted kernel maintenance, not an emergency, unless your fleet includes affected Qualcomm-based Linux devices. The absence of CVSS and exploitation evidence lowers urgency, but kernel NULL dereferences can still affect availability on exposed systems.

Technical view

The flaw is in drm/msm/dsi msm_dsi_phy_enable. The function derived dev from phy before validating phy, so a NULL phy could be dereferenced. Stable kernel commits move dev initialization after the sanity check. Source evidence does not define triggerability, required privileges, or practical exploit impact.

Likely exposure

Likely exposure is limited to Linux systems running affected kernel versions with the MSM DSI/DRM display driver path present, commonly relevant to Qualcomm-based devices. Generic Linux servers may be unaffected if this driver is absent or unused, but kernel build configuration and vendor backports must be checked.

Exploitation context

The CVE bundle marks KEV as false and cites no active exploitation. No public exploit status is provided. The described weakness is a possible kernel NULL pointer dereference, so the most defensible concern is reliability or denial-of-service risk, not proven code execution.

Researcher notes

Evidence is sparse: no CWE, CVSS, exploitability analysis, or trigger path is provided. Analysis should focus on affected kernel lineage, driver configuration, and whether downstream vendors incorporated one of the stable commits. Avoid assuming broader Linux exposure without MSM DSI relevance.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Use distro or device-vendor advisories to confirm the backported patch level.
  • Prioritize Qualcomm MSM display-driver devices over unrelated Linux hosts.
  • If patching is delayed, review whether the MSM DSI driver is built or reachable.

Validation and detection

  • Inventory kernel versions and vendor patch levels across Linux assets.
  • Confirm whether MSM DSI or DRM MSM support is enabled in relevant kernels.
  • Check kernel changelogs for the referenced stable commit identifiers.
  • Document vendor confirmation when fixed versions are backported without upstream version numbers.
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-48756 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
2ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5c8290284402bf7d2c12269402b3177b899c78b7, 5c8290284402bf7d2c12269402b3177b899c78b7, 5c8290284402bf7d2c12269402b3177b899c78b7, 5c8290284402bf7d2c12269402b3177b899c78b7, 5c8290284402bf7d2c12269402b3177b899c78b7, 5c8290284402bf7d2c12269402b3177b899c78b7, 5c8290284402bf7d2c12269402b3177b899c78b7unaffected
LinuxLinux4.3, 0, 4.14.265, 4.19.228, 5.4.176, 5.10.96, 5.15.19, 5.16.5, 5.17affected
Weakness

CWE details

No CWE listed

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