LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50134: RDMA/hfi1: fix potential memory leak in setup_base_ctxt()

In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: fix potential memory leak in setup_base_ctxt() setup_base_ctxt() allocates a memory chunk for uctxt->groups with hfi1_alloc_ctxt_rcv_groups(). When init_user_ctxt() fails, uctxt->groups is not released, which will lead to a memory leak. We should release the uctxt->groups with hfi1_free_ctxt_rcv_groups() when init_user_ctxt() fails.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50134 is a Linux kernel issue in the RDMA hfi1 driver. A failed user-context initialization can leave allocated memory unreleased. The public record does not provide CVSS, confirmed exploitation, or a full impact analysis. Business urgency is highest for Linux systems that use hfi1/RDMA, commonly in specialized high-performance computing environments.

Executive priority

Treat as targeted kernel maintenance, not an emergency, unless hfi1/RDMA is business-critical. Prioritize HPC or specialized Linux clusters first. The absence of CVSS and exploitation evidence lowers urgency, but kernel memory leaks should still be remediated through normal patch cycles.

Technical view

The flaw is a memory leak in RDMA/hfi1 setup_base_ctxt(). uctxt->groups is allocated by hfi1_alloc_ctxt_rcv_groups(), but was not freed if init_user_ctxt() failed. The fix frees that allocation with hfi1_free_ctxt_rcv_groups() on the failure path. Linux stable commits are referenced as the remediation source.

Likely exposure

Exposure appears limited to Linux systems with the hfi1 RDMA driver path present and usable. The source lists Linux kernel versions including 4.14 through 6.0 as affected data, with stable kernel commits referenced. Systems without hfi1/RDMA use are likely lower priority, but should still follow distribution guidance.

Exploitation context

No CISA KEV listing is provided, and the source bundle does not cite active exploitation or public exploit details. The described impact is a potential memory leak, which may affect availability if the vulnerable failure path can be repeatedly reached. The sources do not establish remote reachability or privilege requirements.

Researcher notes

Evidence is limited to the CVE record and Linux stable fix references. The record identifies the failure path and corrective free operation, but does not provide CVSS, CWE, exploitability, or downstream distribution status. Avoid assuming reachability beyond RDMA/hfi1 contexts without local validation.

Mitigation direction

  • Check Linux vendor or distribution advisories for CVE-2022-50134 applicability.
  • Apply a kernel update containing the referenced RDMA/hfi1 memory-leak fix.
  • Prioritize systems using hfi1/RDMA or high-performance computing workloads.
  • If no update is available, follow vendor guidance rather than applying ad hoc changes.

Validation and detection

  • Inventory Linux systems for hfi1/RDMA driver use.
  • Confirm the running kernel includes a referenced stable fix or downstream backport.
  • Review kernel package changelogs for CVE-2022-50134 or setup_base_ctxt().
  • Track distribution advisory status for affected kernel branches.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50134 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe87473bc1b6c2cb08f1b760cfc8cd012822241a6, e87473bc1b6c2cb08f1b760cfc8cd012822241a6, e87473bc1b6c2cb08f1b760cfc8cd012822241a6, e87473bc1b6c2cb08f1b760cfc8cd012822241a6, e87473bc1b6c2cb08f1b760cfc8cd012822241a6, e87473bc1b6c2cb08f1b760cfc8cd012822241a6, e87473bc1b6c2cb08f1b760cfc8cd012822241a6, e87473bc1b6c2cb08f1b760cfc8cd012822241a6unaffected
LinuxLinux4.14, 0, 4.14.291, 4.19.256, 5.4.211, 5.10.137, 5.15.61, 5.18.18, 5.19.2, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.