CVE-2022-49483: drm/msm/disp/dpu1: avoid clearing hw interrupts if hw_intr is null during drm uninit
In the Linux kernel, the following vulnerability has been resolved:
drm/msm/disp/dpu1: avoid clearing hw interrupts if hw_intr is null during drm uninit
If edp modeset init is failed due to panel being not ready and
probe defers during drm bind, avoid clearing irqs and dereference
hw_intr when hw_intr is null.
BUG: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
Call trace:
dpu_core_irq_uninstall+0x50/0xb0
dpu_irq_uninstall+0x18/0x24
msm_drm_uninit+0xd8/0x16c
msm_drm_bind+0x580/0x5fc
try_to_bring_up_master+0x168/0x1c0
__component_add+0xb4/0x178
component_add+0x1c/0x28
dp_display_probe+0x38c/0x400
platform_probe+0xb0/0xd0
really_probe+0xcc/0x2c8
__driver_probe_device+0xbc/0xe8
driver_probe_device+0x48/0xf0
__device_attach_driver+0xa0/0xc8
bus_for_each_drv+0x8c/0xd8
__device_attach+0xc4/0x150
device_initial_probe+0x1c/0x28
Changes in V2:
- Update commit message and coreect fixes tag.
Patchwork: https://patchwork.freedesktop.org/patch/484430/
Security readout for executives and security teams
Plain-English summary
This Linux kernel flaw can crash affected systems by hitting a null pointer in the Qualcomm MSM/DPU display driver cleanup path. The known impact is availability loss, not data theft or privilege escalation. It matters most for devices using this display stack, especially embedded, mobile, or appliance-like Linux builds.
Executive priority
Schedule remediation through normal kernel update cycles, with higher urgency for managed devices where local users can trigger display initialization paths. This is not supported as internet-exploited or data-impacting in the provided sources.
Technical view
CVE-2022-49483 is a CWE-476 null pointer dereference in drm/msm/disp/dpu1 during DRM uninitialization. If eDP modeset initialization fails because the panel is not ready and probe defers, cleanup may dereference a null hw_intr while clearing interrupts, causing a kernel crash.
Likely exposure
Exposure appears limited to Linux systems using the Qualcomm MSM DPU display path in affected kernel builds. Generic servers without this hardware or driver path are less likely exposed. The source bundle lists Linux kernel versions and stable commits, but distro backports require vendor-specific verification.
Exploitation context
The CVSS vector is local, low complexity, and requires low privileges, with high availability impact only. The bundle does not cite KEV inclusion or any active exploitation. Treat this as a local denial-of-service risk unless additional vendor evidence shows broader impact.
Researcher notes
The failure path occurs when eDP panel readiness causes deferred probe during DRM bind, then DRM uninit clears IRQs while hw_intr is null. Useful validation should focus on kernel configuration, hardware presence, and whether cited stable commits or distro backports are present.
Mitigation direction
Update to a kernel containing the cited stable fixes.
Check your Linux distribution or device vendor advisory for backported patches.
Prioritize Qualcomm MSM/DPU-based devices and embedded Linux images.
If patching is delayed, limit local user access on exposed devices.
Track kernel package status through standard vulnerability management tooling.
Validation and detection
Inventory systems running Qualcomm MSM/DPU display drivers.
Compare running kernel builds against vendor fixed-package guidance.
Review kernel logs for crashes in dpu_core_irq_uninstall or msm_drm_uninit.
Confirm patched source includes the null hw_intr guard during IRQ cleanup.
Validate remediation with vendor-supported kernel packages, not only upstream version numbers.
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-476: 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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-476 · source CWE mapping
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.