CVE-2021-47657: drm/virtio: Ensure that objs is not NULL in virtio_gpu_array_put_free()
In the Linux kernel, the following vulnerability has been resolved:
drm/virtio: Ensure that objs is not NULL in virtio_gpu_array_put_free()
If virtio_gpu_object_shmem_init() fails (e.g. due to fault injection, as it
happened in the bug report by syzbot), virtio_gpu_array_put_free() could be
called with objs equal to NULL.
Ensure that objs is not NULL in virtio_gpu_array_put_free(), or otherwise
return from the function.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel availability bug in the virtio GPU driver. A local authenticated user could trigger a crash if an allocation path fails and cleanup handles a NULL object list incorrectly. The reported impact is denial of service only, not data theft or privilege escalation.
Executive priority
Treat this as a routine but real availability risk. It is not currently evidenced as exploited and needs local access, but systems hosting untrusted users or virtualized workloads should receive normal kernel patch priority.
Technical view
CVE-2021-47657 is a CWE-476 NULL pointer dereference in drm/virtio. If virtio_gpu_object_shmem_init() fails, virtio_gpu_array_put_free() may receive objs == NULL. The fix adds a NULL check and returns. CVSS 3.1 is 5.5, local attack vector, low complexity, low privileges, and high availability impact.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions with the virtio GPU DRM driver reachable. This commonly matters for virtualized Linux guests using virtio-gpu. The source bundle lists affected Linux versions and upstream stable fix commits but does not provide distribution-specific package status.
Exploitation context
The source bundle does not show active exploitation, and KEV status is false. The vulnerability requires local privileges and affects availability. The underlying trigger involves a failure path, reported via syzbot fault injection, so real-world exploitability is not established by the provided sources.
Researcher notes
The evidence supports a local denial-of-service assessment only. The CVE record identifies affected upstream Linux versions and four stable commits. It does not identify exploitation in the wild, affected distributions, or additional impacts beyond availability.
Mitigation direction
Apply a kernel update containing the referenced upstream stable fixes.
Check your Linux distribution advisory for backported package status.
Prioritize shared or multi-user virtualized Linux systems using virtio-gpu.
Limit untrusted local shell access where affected kernels remain deployed.
Avoid driver configuration changes unless validated by your OS vendor.
Validation and detection
Inventory Linux kernel versions against the affected versions in the CVE record.
Confirm whether virtio GPU DRM support is enabled or loaded.
Check distro changelogs for the referenced stable commit backports.
Review kernel logs for virtio-gpu related NULL dereference crashes.
Verify patched kernels include the NULL guard in virtio_gpu_array_put_free().
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.