LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50288: qlcnic: prevent ->dcb use-after-free on qlcnic_dcb_enable() failure

In the Linux kernel, the following vulnerability has been resolved: qlcnic: prevent ->dcb use-after-free on qlcnic_dcb_enable() failure adapter->dcb would get silently freed inside qlcnic_dcb_enable() in case qlcnic_dcb_attach() would return an error, which always happens under OOM conditions. This would lead to use-after-free because both of the existing callers invoke qlcnic_dcb_get_info() on the obtained pointer, which is potentially freed at that point. Propagate errors from qlcnic_dcb_enable(), and instead free the dcb pointer at callsite using qlcnic_dcb_free(). This also removes the now unused qlcnic_clear_dcb_ops() helper, which was a simple wrapper around kfree() also causing memory leaks for partially initialized dcb. Found by Linux Verification Center (linuxtesting.org) with the SVACE static analysis tool.

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-50288 is a Linux kernel memory-safety bug in the qlcnic network driver. Under out-of-memory conditions, driver setup can free a DCB pointer and later reuse it. The source does not provide CVSS, confirmed impact, or evidence of exploitation, so urgency depends on affected kernel use and whether qlcnic is present.

Executive priority

Treat this as a kernel hygiene issue with uncertain severity, not a confirmed emergency. Prioritize routine kernel updates, with faster handling for systems using qlcnic hardware or drivers in production.

Technical view

The flaw is a use-after-free in qlcnic_dcb_enable() error handling. When qlcnic_dcb_attach() fails, adapter->dcb can be freed while callers still invoke qlcnic_dcb_get_info() on the pointer. Kernel stable fixes propagate the error and free the DCB object at the call site.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the qlcnic driver and DCB-related code path reachable. The source lists affected Linux versions from 3.14 through 6.2 and stable fix commits, but does not define distribution package status.

Exploitation context

No active exploitation is cited, and the CVE is not marked KEV in the bundle. The triggering condition described is qlcnic_dcb_attach() failure under out-of-memory conditions. The public source does not provide a proof of concept or exploitation impact.

Researcher notes

Evidence is source-limited: no CVSS, CWE, exploitability assessment, or distribution-specific package data is provided. The strongest technical signal is a kernel use-after-free reachable during OOM-triggered driver error handling, fixed by correcting ownership and error propagation.

Mitigation direction

  • Check vendor kernel advisories and distribution package status for CVE-2022-50288.
  • Update affected kernels to versions containing the referenced stable fixes.
  • Prioritize hosts using the qlcnic driver or related network hardware.
  • If patching is delayed, assess whether qlcnic is loaded and operationally required.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Check whether the qlcnic module is present, loaded, or required.
  • Map installed kernels to distribution advisories or the referenced stable commits.
  • Confirm patched systems include the qlcnic DCB error-handling fix.
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-50288 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
LinuxLinux3c44bba1d270cb1620b4fe76786d0968118cb86b, 3c44bba1d270cb1620b4fe76786d0968118cb86b, 3c44bba1d270cb1620b4fe76786d0968118cb86b, 3c44bba1d270cb1620b4fe76786d0968118cb86b, 3c44bba1d270cb1620b4fe76786d0968118cb86b, 3c44bba1d270cb1620b4fe76786d0968118cb86b, 3c44bba1d270cb1620b4fe76786d0968118cb86b, 3c44bba1d270cb1620b4fe76786d0968118cb86bunaffected
LinuxLinux3.14, 0, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.87, 6.0.19, 6.1.5, 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.