Security readout for executives and security teams
Plain-English summary
This Linux kernel flaw can crash affected systems when the MSM DisplayPort driver mishandles a rare display shutdown race. The business impact is availability: a local user process can trigger a kernel panic, but the sources do not indicate data theft, privilege escalation, or remote exploitation.
Executive priority
Treat as a targeted availability risk, not a broad internet-facing emergency. Prioritize patching exposed fleets where local users or managed display sessions run on affected MSM DisplayPort hardware.
Technical view
The issue is in drm/msm/dp. A userspace display manager can set crtc->active during an extra screen update after the downstream display path is disabled. drm_release() may then call dp_bridge_disable(), which touches main link registers while clocks are disabled, causing an arm64 SError panic.
Likely exposure
Exposure is most likely on Linux systems using the MSM DisplayPort driver and affected kernel versions listed by the CVE source bundle. The bundle names Linux 5.17, 6.0.7, and 6.1 entries, but exact distro backport status must be verified with kernel vendor packages.
Exploitation context
The CVE is not marked KEV, and the provided sources do not state active exploitation. The CVSS vector is local, low complexity, low privileges, no user interaction, with high availability impact only.
Researcher notes
Evidence supports a kernel panic caused by double-disable handling in the DRM bridge path. The fix adds atomic_check to prevent pushing a frame when the display interface is down. Source evidence is specific but incomplete for downstream distro version mapping.
Mitigation direction
- Apply Linux kernel updates containing the referenced stable fixes.
- Check distro or device-vendor advisories for backported kernel packages.
- Prioritize systems using Qualcomm MSM DisplayPort hardware paths.
- If no fixed package exists, follow vendor guidance for operational workarounds.
Validation and detection
- Inventory affected systems by kernel version and MSM DisplayPort usage.
- Confirm installed kernels include the referenced stable commits or vendor backports.
- Review kernel logs for dp_bridge_disable, dp_ctrl_push_idle, or SError panic traces.
- After updating, verify systems no longer match affected kernel entries.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2022-50398 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.