# nvmet: fix a memory leak in nvmet_auth_set_key

CVE record · `CVE-2022-49807`

- **Identifiers:** `CVE-2022-49807`
- **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: `db1312dd95488b5e6ff362ff66fcf953a46b1821 to before 65710ea51d4a185592c7b14c9e33d0c4a364f074` (git)
  - affected: `db1312dd95488b5e6ff362ff66fcf953a46b1821 to before 0a52566279b4ee65ecd2503d7b7342851f84755c` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.0`
  - unaffected: `before 6.0` (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.

> Linux kernel versions from db1312dd95488b5e6ff362ff66fcf953a46b1821 up to the fixes 65710ea51d4a185592c7b14c9e33d0c4a364f074 and 0a52566279b4ee65ecd2503d7b7342851f84755c are affected, which covers the 6.0 series before the fix. The source describes a memory leak in the NVMe target's DH-HMAC-CHAP authentication code, where old secrets were not released when new ones were set through configfs. The source gives few details about who can trigger it or what impact it has beyond the leak. Upgrade to a kernel that includes the fix, such as 6.0.10 or later in the 6.0 series or 6.1 and 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-49807)
- 1 May 2025, 15:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-49807)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/65710ea51d4a185592c7b14c9e33d0c4a364f074>
- <https://git.kernel.org/stable/c/0a52566279b4ee65ecd2503d7b7342851f84755c>

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

---

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