# powerpc/papr_scm: Fix leaking nvdimm_events_map elements

CVE record · `CVE-2022-49436`

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

Published by the CVE Program (CNA: Linux) at 26 Feb 2025, 02:12 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: `4c08d4bbc089a95f3f38389c2b79dbc6ab24f10b to before b073096df4dec70d0436321b7093bad27ae91f9e` (git)
  - affected: `4c08d4bbc089a95f3f38389c2b79dbc6ab24f10b to before 0e0946e22f3665d27325d389ff45ade6e93f3678` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.18`
  - unaffected: `before 5.18` (semver)
  - unaffected: `5.18.3 to 5.18.*, inclusive` (semver)
  - unaffected: `5.19 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's PowerPC papr_scm driver leaks memory allocated for performance event identifiers in its removal and registration error paths, affecting Linux 5.18 before 5.18.3. The source gives few details on how the leak could be triggered or what an attacker could gain. Upgrade to Linux 5.18.3 or 5.19 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.0022, the 13th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 26 Feb 2025, 02:12 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-49436)
- 26 Feb 2025, 07:01 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-49436)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/b073096df4dec70d0436321b7093bad27ae91f9e>
- <https://git.kernel.org/stable/c/0e0946e22f3665d27325d389ff45ade6e93f3678>

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

---

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