CVE-2022-50181: virtio-gpu: fix a missing check to avoid NULL dereference
In the Linux kernel, the following vulnerability has been resolved:
virtio-gpu: fix a missing check to avoid NULL dereference
'cache_ent' could be set NULL inside virtio_gpu_cmd_get_capset()
and it will lead to a NULL dereference by a lately use of it
(i.e., ptr = cache_ent->caps_cache). Fix it with a NULL check.
[ kraxel: minor codestyle fixup ]
Security readout for executives and security teams
Plain-English summary
CVE-2022-50181 is a Linux kernel virtio-gpu bug where a missing NULL check can cause a NULL pointer dereference. In business terms, the credible concern is system or workload instability on affected Linux systems using virtio-gpu, not proven data theft or active compromise based on the provided sources.
Executive priority
Handle through normal kernel patch governance, with higher priority for virtualization-heavy environments using virtio-gpu. There is no provided evidence of active exploitation or critical impact, but kernel stability issues can still affect service availability.
Technical view
The flaw is in virtio_gpu_cmd_get_capset(). The CVE states cache_ent can become NULL, then later code dereferences cache_ent->caps_cache. Upstream stable references show fixes adding a NULL check. The source bundle provides no CVSS, CWE, exploit primitive, or privilege context.
Likely exposure
Exposure is most likely on Linux systems that use the virtio-gpu driver, commonly in virtualized graphics scenarios. The CVE data lists affected Linux versions including 4.4, 5.10.137, 5.15.61, 5.18.18, 5.19.2, and 6.0, but distribution package status must be verified separately.
Exploitation context
The provided bundle does not show active exploitation, public exploit availability, or inclusion in CISA KEV. It only describes a resolved NULL dereference. Treat exploitation likelihood and required attacker position as unconfirmed until vendor advisories provide more context.
Researcher notes
The record is sparse: no CVSS, CWE, threat model, or trigger conditions are included. Analysis should focus on commit review, affected stable branches, distribution backports, and whether local virtio-gpu exposure exists. Do not infer remote code execution from this source bundle.
Mitigation direction
Update to kernel packages that include the referenced upstream stable fixes.
Check Linux distribution advisories for CVE-2022-50181 package status.
Prioritize systems using virtio-gpu or virtualized graphics paths.
Track vendor guidance if no fixed package is available yet.
Validation and detection
Inventory Linux kernel versions across virtualization hosts and guests.
Confirm whether virtio-gpu is present or enabled on relevant systems.
Map installed kernels against distribution advisories for this CVE.
Verify patched kernels include the referenced upstream stable commits.
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-50181 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
3Timeline events
0ADP providers
6Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jun 18, 2025, 11:03 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.