# io_uring: fix multishot accept request leaks

CVE record · `CVE-2022-49791`

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

Published by the CVE Program (CNA: Linux) at 1 May 2025, 14:09 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: `390ed29b5e425ba00da2b6113b74a14949f71b02 to before 0e4626de856ef8f25ecd9c716e76d4f95ce95639` (git)
  - affected: `390ed29b5e425ba00da2b6113b74a14949f71b02 to before 91482864768a874c4290ef93b84a78f4f1dac51b` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.19`
  - unaffected: `before 5.19` (semver)
  - unaffected: `6.0.10 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 Linux kernel io_uring component is affected starting with version 5.19. A flaw in multishot accept handling causes requests to leak, so kernel resources are not released. The source does not say what access an attacker needs. Upgrade to Linux 6.0.10 or later in the 6.0 series, or to 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.0017, the 6th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

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

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/0e4626de856ef8f25ecd9c716e76d4f95ce95639>
- <https://git.kernel.org/stable/c/91482864768a874c4290ef93b84a78f4f1dac51b>

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

---

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