LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50842: drm/virtio: Check whether transferred 2D BO is shmem

In the Linux kernel, the following vulnerability has been resolved: drm/virtio: Check whether transferred 2D BO is shmem Transferred 2D BO always must be a shmem BO. Add check for that to prevent NULL dereference if userspace passes a VRAM BO.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-50842 is a Linux kernel virtio DRM flaw where an invalid graphics buffer type can trigger a NULL pointer dereference. The available sources describe a stability issue, not data theft or remote takeover. Business urgency is highest for Linux systems using virtio graphics, especially virtualized desktops or hosts exposing virtio-gpu to untrusted local users.

Executive priority

Treat as a targeted Linux availability risk, not an emergency internet-wide issue based on current evidence. Prioritize patch validation for virtualized Linux environments using virtio graphics, especially where untrusted local users can interact with graphics devices.

Technical view

In drm/virtio, transferred 2D buffer objects must be shmem-backed. The fix adds a type check because userspace could pass a VRAM BO and reach a NULL dereference path. Public data lists Linux kernel impact and stable kernel commits, but provides no CVSS, CWE, or detailed exploitability assessment.

Likely exposure

Likely exposure is Linux systems with the virtio DRM/virtio-gpu path available to local userspace. Systems not using virtio graphics are less likely to be affected. Version data in the source bundle is incomplete and should be confirmed against distribution advisories and kernel backport status.

Exploitation context

The source states userspace can pass a VRAM buffer object, causing a NULL dereference. No provided source or KEV entry indicates active exploitation. The described access path appears local/userspace rather than network-facing, with the most plausible impact being kernel instability or denial of service.

Researcher notes

The key condition is a transferred 2D BO that is not shmem-backed. The patch adds validation before use to prevent a NULL dereference when a VRAM BO is supplied. Public metadata lacks CVSS and detailed affected-range clarity, so distro-specific kernel mapping is important.

Mitigation direction

  • Update to a kernel containing the referenced stable virtio DRM fix.
  • Check Linux distribution advisories for backported fixes.
  • Prioritize virtualized systems that expose virtio graphics to untrusted users.
  • Disable or avoid virtio graphics exposure where operationally feasible, pending vendor guidance.

Validation and detection

  • Inventory Linux systems using virtio DRM or virtio-gpu.
  • Compare running kernel builds against vendor advisories and stable commit backports.
  • Confirm whether distribution kernels include the referenced fix commits.
  • Review crash reports for virtio DRM NULL dereference indicators.
Prepared
Confidence
medium
Sources
7

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-50842 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf651c8b055423057d9f41525dfdc37b4796015d1, f651c8b055423057d9f41525dfdc37b4796015d1, f651c8b055423057d9f41525dfdc37b4796015d1, f651c8b055423057d9f41525dfdc37b4796015d1, f651c8b055423057d9f41525dfdc37b4796015d1unaffected
LinuxLinux5.7, 0, 5.10.150, 5.15.75, 5.19.17, 6.0.3, 6.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.