# io_uring/msg_ring: Fix NULL pointer dereference in io_msg_send_fd()

CVE record · `CVE-2022-50295`

- **Identifiers:** `CVE-2022-50295`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 15 Sept 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 15 Sept 2025, 14:45 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: `e6130eba8a848a7a6ba6c534bd8f6d60749ae1a9 to before 0163e04ea64cc3dfaa12390286e5f2f481c3b2e3` (git)
  - affected: `e6130eba8a848a7a6ba6c534bd8f6d60749ae1a9 to before 16bbdfe5fb0e78e0acb13e45fc127e9a296913f2` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.0`
  - unaffected: `before 6.0` (semver)
  - unaffected: `6.0.6 to 6.0.*, inclusive` (semver)
  - unaffected: `6.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The io_uring msg_ring component in the Linux kernel is affected in version 6.0 and in some development builds before the fix. A missing NULL check in io_msg_send_fd() can cause a NULL pointer dereference that crashes the kernel. The source gives few details on what an attacker needs. Upgrade to Linux kernel 6.0.6 or 6.1 or later.

Written 16 Nov 2026.

## 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.0014, the 3rd percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 15 Sept 2025, 14:45 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-50295)
- 15 Sept 2025, 15:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-50295)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/0163e04ea64cc3dfaa12390286e5f2f481c3b2e3>
- <https://git.kernel.org/stable/c/16bbdfe5fb0e78e0acb13e45fc127e9a296913f2>

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-50295>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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