LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50025: cxl: Fix a memory leak in an error handling path

In the Linux kernel, the following vulnerability has been resolved: cxl: Fix a memory leak in an error handling path A bitmap_zalloc() must be balanced by a corresponding bitmap_free() in the error handling path of afu_allocate_irqs().

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-50025 is a Linux kernel memory leak in the cxl driver error path. When IRQ allocation fails, allocated bitmap memory was not freed. This is not listed as actively exploited and has no CVSS score in the provided sources. Business risk appears limited, but affected Linux kernels should be updated through normal kernel maintenance.

Executive priority

Handle through routine Linux kernel patching unless your environment depends on the affected cxl driver path. There is no sourced evidence of active exploitation or remote attack exposure, but kernel memory leaks can still affect system stability in specific conditions.

Technical view

The issue is in afu_allocate_irqs(): bitmap_zalloc() was not balanced with bitmap_free() during error handling. The CVE record says the vulnerability is resolved by Linux stable commits across maintained branches. The sources do not provide exploitability details, a CWE, or a CVSS score.

Likely exposure

Exposure is most likely on Linux systems running affected kernel builds where the cxl driver code path is present and usable. It is not described as a remotely reachable network service issue. Exact affected distribution packages require vendor mapping or changelog confirmation.

Exploitation context

CISA KEV status is false in the provided bundle, and no cited source reports active exploitation. Practical exploitation would require triggering the relevant kernel driver error path; the sources do not document an exploit path or prerequisites.

Researcher notes

The public record is sparse: no CVSS, CWE, exploit status, or detailed trigger conditions are provided. The core fix is a cleanup correction in an error path. Treat distribution impact carefully because vendor kernels may backport fixes without changing upstream version numbers.

Mitigation direction

  • Update affected Linux kernels using vendor-supported packages.
  • Confirm the update includes the referenced upstream stable fix.
  • Check distribution advisories for backported fixes.
  • Prioritize systems using the cxl driver or related accelerator hardware.
  • If unsure, follow your Linux vendor’s CVE guidance.

Validation and detection

  • Record running kernel versions across Linux assets.
  • Check vendor changelogs for CVE-2022-50025 or the stable commit IDs.
  • Verify patched kernels are booted, not only installed.
  • Assess whether the cxl driver is present or used on priority systems.
  • Document exceptions where vendor status is unavailable.
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-50025 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
LinuxLinux80fa93fce37d3490f4bb0da8a5b239a6745bc744, 80fa93fce37d3490f4bb0da8a5b239a6745bc744, 80fa93fce37d3490f4bb0da8a5b239a6745bc744, 80fa93fce37d3490f4bb0da8a5b239a6745bc744, 80fa93fce37d3490f4bb0da8a5b239a6745bc744, 80fa93fce37d3490f4bb0da8a5b239a6745bc744, 80fa93fce37d3490f4bb0da8a5b239a6745bc744, 80fa93fce37d3490f4bb0da8a5b239a6745bc744unaffected
LinuxLinux3.19, 0, 4.9.326, 4.14.291, 4.19.256, 5.4.211, 5.10.138, 5.15.63, 5.19.4, 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.