CVE-2022-48749: drm/msm/dpu: invalid parameter check in dpu_setup_dspp_pcc
In the Linux kernel, the following vulnerability has been resolved:
drm/msm/dpu: invalid parameter check in dpu_setup_dspp_pcc
The function performs a check on the "ctx" input parameter, however, it
is used before the check.
Initialize the "base" variable after the sanity check to avoid a
possible NULL pointer dereference.
Addresses-Coverity-ID: 1493866 ("Null pointer dereference")
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel bug in the Qualcomm msm display driver path. A bad null check could let the kernel dereference a missing context pointer, potentially causing a crash. The source bundle does not provide CVSS, confirmed impact, or active exploitation evidence.
Executive priority
Handle through normal kernel patch management unless affected Qualcomm msm display systems are business-critical or difficult to recover. There is a credible stability risk, but the available sources do not support emergency prioritization.
Technical view
The issue is in drm/msm/dpu, function dpu_setup_dspp_pcc. The code initializes or uses a base value derived from ctx before validating ctx, creating a possible NULL pointer dereference. Stable kernel commits move initialization after the sanity check.
Likely exposure
Exposure appears limited to Linux kernels with the affected drm/msm/dpu code, especially systems using Qualcomm msm DPU display components. The bundle lists affected Linux versions including 5.8, 5.10.96, 5.15.19, 5.16.5, and 5.17, but does not define downstream distribution status.
Exploitation context
The bundle provides no evidence of active exploitation, and kev is false. It also does not state whether the vulnerable path is reachable remotely, locally, or only through specific display-driver operations. Treat exploitation context as unconfirmed.
Researcher notes
Focus validation on reachability of dpu_setup_dspp_pcc in affected kernels and whether downstream kernels carried the fix. Do not infer privilege requirements, remote exposure, or exploitability from the null dereference description alone.
Mitigation direction
Upgrade to a kernel containing the referenced stable fixes.
Check your distribution or device vendor guidance for backported fixes.
Prioritize systems using Qualcomm msm or DPU display hardware paths.
Track downstream kernel advisory status before assuming version numbers alone are decisive.
Validation and detection
Inventory Linux kernel versions across affected device classes.
Identify systems using the drm/msm DPU display driver path.
Confirm whether vendor kernels include one of the referenced fixes.
Verify CISA KEV status remains negative before changing exploitation assumptions.
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-48749 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.