# nvmem: core: Fix memleak in nvmem_register()

CVE record · `CVE-2022-50734`

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

Published by the CVE Program (CNA: Linux) at 24 Dec 2025, 12:22 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: `de0534df93474f268486c486ea7e01b44a478026 to before 9391cc3a787a58aa224a6440d7f244d780ba2896` (git)
  - affected: `de0534df93474f268486c486ea7e01b44a478026 to before 2bd2774df0ce37920b23819a860a66fdbdd90823` (git)
  - affected: `de0534df93474f268486c486ea7e01b44a478026 to before b6054b9b239a493672f853b034570cca93ba7a88` (git)
  - affected: `de0534df93474f268486c486ea7e01b44a478026 to before bd1244561fa2a4531ded40dbf09c9599084f8b29` (git)
  - affected: `c1d44b93ca9f3ebc26b0de0a7f4b7156702762b6` (git)
  - affected: `63c2b13ba0428b8f477e4adb1d40a50eb4493c09` (git)
  - affected: `5.13.19 to before 5.14` (semver)
  - affected: `5.14.6 to before 5.15` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.15`
  - unaffected: `before 5.15` (semver)
  - unaffected: `5.15.75 to 5.15.*, inclusive` (semver)
  - unaffected: `5.19.17 to 5.19.*, inclusive` (semver)
  - unaffected: `6.0.3 to 6.0.*, inclusive` (semver)
  - unaffected: `6.1 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

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0024, the 15th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 24 Dec 2025, 13:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-50734)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/9391cc3a787a58aa224a6440d7f244d780ba2896>
- <https://git.kernel.org/stable/c/2bd2774df0ce37920b23819a860a66fdbdd90823>
- <https://git.kernel.org/stable/c/b6054b9b239a493672f853b034570cca93ba7a88>
- <https://git.kernel.org/stable/c/bd1244561fa2a4531ded40dbf09c9599084f8b29>

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

---

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