# apparmor: Fix memleak in alloc_ns()

CVE record · `CVE-2022-50860`

- **Identifiers:** `CVE-2022-50860`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 30 Dec 2025
- **Updated:** 5 Aug 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 30 Dec 2025, 12:15 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: `a1bd627b46d169268a0ee5960899fb5be960a317 to before 9a32aa87a25d800b2c6f47bc2749a7bfd9a486f3` (git)
  - affected: `a1bd627b46d169268a0ee5960899fb5be960a317 to before 5f509fa740b17307f0cba412485072f632d5af36` (git)
  - affected: `a1bd627b46d169268a0ee5960899fb5be960a317 to before 0250cf8d37bb5201a117177afd24dc73a1c81657` (git)
  - affected: `a1bd627b46d169268a0ee5960899fb5be960a317 to before 12695b4b76d437b9c0182a6f7dfb2248013a9daf` (git)
  - affected: `a1bd627b46d169268a0ee5960899fb5be960a317 to before e9e6fa49dbab6d84c676666f3fe7d360497fd65b` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.13`
  - unaffected: `before 4.13` (semver)
  - unaffected: `5.10.163 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.86 to 5.15.*, inclusive` (semver)
  - unaffected: `6.0.16 to 6.0.*, inclusive` (semver)
  - unaffected: `6.1.2 to 6.1.*, inclusive` (semver)
  - unaffected: `6.2 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

- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (Linux)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0020, the 10th percentile, on 19 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 30 Dec 2025. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/9a32aa87a25d800b2c6f47bc2749a7bfd9a486f3>
- <https://git.kernel.org/stable/c/5f509fa740b17307f0cba412485072f632d5af36>
- <https://git.kernel.org/stable/c/0250cf8d37bb5201a117177afd24dc73a1c81657>
- <https://git.kernel.org/stable/c/12695b4b76d437b9c0182a6f7dfb2248013a9daf>
- <https://git.kernel.org/stable/c/e9e6fa49dbab6d84c676666f3fe7d360497fd65b>

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

---

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