CVE-2022-49489: drm/msm/disp/dpu1: set vbif hw config to NULL to avoid use after memory free during pm runtime resume
In the Linux kernel, the following vulnerability has been resolved:
drm/msm/disp/dpu1: set vbif hw config to NULL to avoid use after memory free during pm runtime resume
BUG: Unable to handle kernel paging request at virtual address 006b6b6b6b6b6be3
Call trace:
dpu_vbif_init_memtypes+0x40/0xb8
dpu_runtime_resume+0xcc/0x1c0
pm_generic_runtime_resume+0x30/0x44
__genpd_runtime_resume+0x68/0x7c
genpd_runtime_resume+0x134/0x258
__rpm_callback+0x98/0x138
rpm_callback+0x30/0x88
rpm_resume+0x36c/0x49c
__pm_runtime_resume+0x80/0xb0
dpu_core_irq_uninstall+0x30/0xb0
dpu_irq_uninstall+0x18/0x24
msm_drm_uninit+0xd8/0x16c
Patchwork: https://patchwork.freedesktop.org/patch/483255/
[DB: fixed Fixes tag]
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel use-after-free in the MSM/DPU display driver path. A local low-privileged user could potentially trigger serious impact on confidentiality, integrity, and availability, according to the CVSS vector. The source bundle does not show public exploitation or CISA KEV listing.
Executive priority
Treat as high priority for affected Linux fleets, especially shared or user-accessible systems. Business urgency depends on whether the MSM/DPU display driver path is present. Patch through normal kernel update channels after validation and regression testing.
Technical view
The resolved bug sets the VBIF hardware config pointer to NULL to avoid use-after-free during PM runtime resume. The crash trace reaches dpu_vbif_init_memtypes and dpu_runtime_resume during MSM DRM teardown/resume behavior. It is classified as CWE-416 with CVSS 3.1 score 7.8.
Likely exposure
Exposure is most likely on Linux systems using affected kernel versions with the drm/msm/disp/dpu1 display stack. The source lists Linux as affected and names versions including 4.19, 4.19.247, 5.4.198, 5.10.121, 5.15.46, 5.17.14, 5.18.3, and 5.19.
Exploitation context
No active exploitation is evidenced in the provided sources, and KEV is false. The CVSS vector indicates local attack, low complexity, low privileges required, and no user interaction. The bundle provides a kernel crash trace and fixed stable commits, but no exploit details.
Researcher notes
The evidence supports a kernel use-after-free fixed in stable commits, but the bundle does not prove exploitability beyond the CVSS assessment. Focus analysis on PM runtime resume, MSM DRM teardown, and whether downstream kernels carried the vulnerable commit before the listed fixes.
Mitigation direction
Update affected Linux kernels through the appropriate vendor or distribution channel.
Confirm the deployed kernel includes the relevant stable fix commits.
Prioritize systems where untrusted users can run local code.
Track vendor advisories if your kernel is downstream or device-specific.
Do not rely on KEV absence as proof of safety.
Validation and detection
Inventory kernel versions across Linux hosts and device images.
Check whether systems use the drm/msm/disp/dpu1 display path.
Compare kernel source or package changelogs against cited stable commits.
Review kernel logs for matching dpu_runtime_resume crash traces.
Confirm vulnerability scanner findings against vendor kernel advisories.
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.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
1CVSS vectors
3Timeline events
1ADP providers
8Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.