LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50242: drivers: net: qlcnic: Fix potential memory leak in qlcnic_sriov_init()

In the Linux kernel, the following vulnerability has been resolved: drivers: net: qlcnic: Fix potential memory leak in qlcnic_sriov_init() If vp alloc failed in qlcnic_sriov_init(), all previously allocated vp needs to be freed.

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-50242 is a Linux kernel issue in the qlcnic network driver. If SR-IOV initialization fails partway through, memory allocated earlier may not be freed. The public record describes a reliability/resource-leak issue, not data theft or code execution.

Executive priority

Treat as routine kernel maintenance unless qlcnic SR-IOV is widely used in critical infrastructure. There is no cited active exploitation or scored severity, but resource leaks in kernel drivers can affect availability over time.

Technical view

The fix frees previously allocated virtual port structures when a later allocation fails in qlcnic_sriov_init(). The CVE record lists Linux as affected and links multiple stable kernel commits. No CVSS score, CWE, or exploitation details are provided in the supplied sources.

Likely exposure

Exposure is most relevant to Linux systems using the qlcnic network driver and SR-IOV functionality. Systems without this driver or hardware path are less likely to be exposed. Confirm against your distribution’s kernel package, because vendor backports may change version-based conclusions.

Exploitation context

The sources do not report active exploitation, and this CVE is not marked KEV. The described condition is an allocation-failure path during driver initialization. Public sources provided do not show remote reachability, privilege requirements, or attacker-controlled triggering details.

Researcher notes

Evidence is limited to the CVE record and kernel stable commits. The vulnerability is a cleanup bug in an error path, not a fully characterized exploit scenario. Validate practical impact by reviewing the driver path and distribution backports, without assuming reachability beyond the published description.

Mitigation direction

  • Update affected Linux kernels using your distribution or vendor kernel packages.
  • Prioritize hosts using qlcnic adapters with SR-IOV enabled.
  • If updates are unavailable, check vendor guidance for supported workarounds.
  • Avoid relying only on upstream version numbers; account for vendor backports.

Validation and detection

  • Inventory Linux hosts and kernel package versions.
  • Check whether the qlcnic driver is present or loaded.
  • Identify systems using SR-IOV with qlcnic-supported hardware.
  • Compare installed kernels with vendor advisories and referenced stable commits.
  • Confirm the fix is included through package changelogs or vendor security metadata.
Prepared
Confidence
medium
Sources
11

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-50242 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
10Source 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
LinuxLinuxf197a7aa62888f27c9a7976b18eb4f040f6606ce, f197a7aa62888f27c9a7976b18eb4f040f6606ce, f197a7aa62888f27c9a7976b18eb4f040f6606ce, f197a7aa62888f27c9a7976b18eb4f040f6606ce, f197a7aa62888f27c9a7976b18eb4f040f6606ce, f197a7aa62888f27c9a7976b18eb4f040f6606ce, f197a7aa62888f27c9a7976b18eb4f040f6606ce, f197a7aa62888f27c9a7976b18eb4f040f6606ce, f197a7aa62888f27c9a7976b18eb4f040f6606ceunaffected
LinuxLinux3.10, 0, 4.9.337, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, 6.2affected
Weakness

CWE details

No CWE listed

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