LiveActive security incident?Get immediate response
CVE Record

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/

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

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.
Prepared
Confidence
high
Sources
6

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-49483 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
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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.

1CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

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

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.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2022-49483Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf25f656608e3a54ac3e0747be415cf3d4a69cef8, f25f656608e3a54ac3e0747be415cf3d4a69cef8, f25f656608e3a54ac3e0747be415cf3d4a69cef8unaffected
LinuxLinux5.16, 0, 5.17.14, 5.18.3, 5.19affected
Weakness

CWE details

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.