# blk-mq: fix possible memleak when register 'hctx' failed

CVE record · `CVE-2022-50434`

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

Published by the CVE Program (CNA: Linux) at 1 Oct 2025, 11:42 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: `67aec14ce87fe25bdfff7dbf468556333df11c4e to before 654870789c3c1b9763316ef1c71d7a449127b175` (git)
  - affected: `67aec14ce87fe25bdfff7dbf468556333df11c4e to before cb186eb47fb9dd327bdefa15f0c5fc55c53a40dd` (git)
  - affected: `67aec14ce87fe25bdfff7dbf468556333df11c4e to before 02bc8bc6eab03c84373281b85cb6e98747172ff7` (git)
  - affected: `67aec14ce87fe25bdfff7dbf468556333df11c4e to before 87fd18016a47ea8ae12641377a390172c4aa97a7` (git)
  - affected: `67aec14ce87fe25bdfff7dbf468556333df11c4e to before e8022da1fa2fdf2fa204b445dd3354e7a66d085a` (git)
  - affected: `67aec14ce87fe25bdfff7dbf468556333df11c4e to before eff45bfbc25a2509a6362dea6e699e14083c693c` (git)
  - affected: `67aec14ce87fe25bdfff7dbf468556333df11c4e to before 4b7fafa5f39b15c3a6ca3b95e534d05d6904cc95` (git)
  - affected: `67aec14ce87fe25bdfff7dbf468556333df11c4e to before 33e8a3f61814ea30615d0fafaf50477975d6c1ca` (git)
  - affected: `67aec14ce87fe25bdfff7dbf468556333df11c4e to before 4b7a21c57b14fbcd0e1729150189e5933f5088e9` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `3.16`
  - unaffected: `before 3.16` (semver)
  - unaffected: `4.9.337 to 4.9.*, inclusive` (semver)
  - unaffected: `4.14.303 to 4.14.*, inclusive` (semver)
  - unaffected: `4.19.270 to 4.19.*, inclusive` (semver)
  - unaffected: `5.4.229 to 5.4.*, inclusive` (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

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Linux kernel blk-mq is affected from version 3.16 until fixed, and it leaks kernel memory when registering a hardware context fails partway through. The source gives few details on how an attacker could trigger this. Upgrade to 4.9.337, 4.14.303, 4.19.270, 5.4.229, or a later release in those series.

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.0018, the 8th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 1 Oct 2025, 11:42 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-50434)
- 1 Oct 2025, 12:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-50434)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/654870789c3c1b9763316ef1c71d7a449127b175>
- <https://git.kernel.org/stable/c/cb186eb47fb9dd327bdefa15f0c5fc55c53a40dd>
- <https://git.kernel.org/stable/c/02bc8bc6eab03c84373281b85cb6e98747172ff7>
- <https://git.kernel.org/stable/c/87fd18016a47ea8ae12641377a390172c4aa97a7>
- <https://git.kernel.org/stable/c/e8022da1fa2fdf2fa204b445dd3354e7a66d085a>
- <https://git.kernel.org/stable/c/eff45bfbc25a2509a6362dea6e699e14083c693c>
- <https://git.kernel.org/stable/c/4b7fafa5f39b15c3a6ca3b95e534d05d6904cc95>
- <https://git.kernel.org/stable/c/33e8a3f61814ea30615d0fafaf50477975d6c1ca>
- <https://git.kernel.org/stable/c/4b7a21c57b14fbcd0e1729150189e5933f5088e9>

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

---

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