# virtio-gpu: fix a missing check to avoid NULL dereference

CVE record · `CVE-2022-50181`

- **Identifiers:** `CVE-2022-50181`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 18 Jun 2025
- **Updated:** 11 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 18 Jun 2025, 11:03 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `62fb7a5e10962ac6ae2a2d2dbd3aedcb2a3e3257 to before 259773fc874258606c0121767a4a27466ff337eb` (git)
  - affected: `62fb7a5e10962ac6ae2a2d2dbd3aedcb2a3e3257 to before 39caef09666c1d8274abf9472c72bcac236dc5fb` (git)
  - affected: `62fb7a5e10962ac6ae2a2d2dbd3aedcb2a3e3257 to before adbdd21983fa292e53aec3eab97306b2961ea887` (git)
  - affected: `62fb7a5e10962ac6ae2a2d2dbd3aedcb2a3e3257 to before 367882a5a9448b5e1ba756125308092d614cb96c` (git)
  - affected: `62fb7a5e10962ac6ae2a2d2dbd3aedcb2a3e3257 to before bd63f11f4c3c46afec07d821f74736161ff6e526` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.4`
  - unaffected: `before 4.4` (semver)
  - unaffected: `5.10.137 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.61 to 5.15.*, inclusive` (semver)
  - unaffected: `5.18.18 to 5.18.*, inclusive` (semver)
  - unaffected: `5.19.2 to 5.19.*, inclusive` (semver)
  - unaffected: `6.0 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0026, the 18th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 18 Jun 2025. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2022-50181](https://www.cve.org/CVERecord?id=CVE-2022-50181)
- [NVD: CVE-2022-50181](https://nvd.nist.gov/vuln/detail/CVE-2022-50181)

### References from the CNA

- <https://git.kernel.org/stable/c/259773fc874258606c0121767a4a27466ff337eb>
- <https://git.kernel.org/stable/c/39caef09666c1d8274abf9472c72bcac236dc5fb>
- <https://git.kernel.org/stable/c/adbdd21983fa292e53aec3eab97306b2961ea887>
- <https://git.kernel.org/stable/c/367882a5a9448b5e1ba756125308092d614cb96c>
- <https://git.kernel.org/stable/c/bd63f11f4c3c46afec07d821f74736161ff6e526>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2022-50181>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2022-50181/>. Everything for agents: <https://agentprime.io/llms.txt>.
