# tracing: Fix memory leak in tracing_read_pipe()

CVE record · `CVE-2022-49801`

- **Identifiers:** `CVE-2022-49801`
- **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: `efbbdaa22bb78761bff8dfdde027ad04bedd47ce to before 2c21ee020ce43d744ecd7f3e9bddfcaafef270ce` (git)
  - affected: `efbbdaa22bb78761bff8dfdde027ad04bedd47ce to before a7d3f8f33c113478737bc61bb32ec5f9a987da7d` (git)
  - affected: `efbbdaa22bb78761bff8dfdde027ad04bedd47ce to before 649e72070cbbb8600eb823833e4748f5a0815116` (git)
  - affected: `840ce9cfc86f89c335625ec297acc0375f82e19b` (git)
  - affected: `5.10.190 to before 5.11` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.12`
  - unaffected: `before 5.12` (semver)
  - unaffected: `5.15.80 to 5.15.*, inclusive` (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 tracing subsystem leaks memory in tracing_read_pipe(), affecting version ranges including 5.10.190 through 5.11 and 5.12. Reading the trace pipe leaves kernel memory allocated and never freed. Upgrade to 5.15.80 or later, 6.0.10 or later, or 6.1 or later, depending on your branch.

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.0020, the 9th 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-49801)
- 1 May 2025, 15:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-49801)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/2c21ee020ce43d744ecd7f3e9bddfcaafef270ce>
- <https://git.kernel.org/stable/c/a7d3f8f33c113478737bc61bb32ec5f9a987da7d>
- <https://git.kernel.org/stable/c/649e72070cbbb8600eb823833e4748f5a0815116>

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

---

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