LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49521: scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()

In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp() If no handler is found in lpfc_complete_unsol_iocb() to match the rctl of a received frame, the frame is dropped and resources are leaked. Fix by returning resources when discarding an unhandled frame type. Update lpfc_fc_frame_check() handling of NOP basic link service.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-49521 is a Linux kernel resource leak in the lpfc SCSI driver. Certain received frames that have no matching handler are dropped without returning resources. The main business concern is potential reliability or availability impact on systems using affected Linux kernels and this driver. Public sources do not show active exploitation or a CVSS score.

Executive priority

Treat this as a targeted infrastructure reliability issue, not an internet-wide emergency based on current evidence. Prioritize patch validation for Linux servers connected to storage environments using the lpfc driver, especially high-availability or business-critical systems.

Technical view

The issue is in lpfc_sli4_send_seq_to_ulp() / lpfc_complete_unsol_iocb() handling. When an unsolicited frame’s rctl has no matching handler, the frame is discarded but associated resources are leaked. Kernel stable fixes return resources when discarding unhandled frame types and adjust lpfc_fc_frame_check() handling for NOP basic link service.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions where the lpfc SCSI driver is present and used. Systems not using this driver are less likely to be exposed. Distribution-specific backports may change practical exposure, so installed kernel build details matter.

Exploitation context

The source bundle does not indicate CISA KEV listing, active exploitation, public exploit availability, or attacker prerequisites. The vulnerability involves handling of received frames, suggesting impact may depend on access to the relevant storage/fabric path. Evidence is insufficient to rate exploitability precisely.

Researcher notes

Severity metadata is incomplete: no CVSS, CWE, or KEV signal is provided. The CVE record maps fixes to multiple stable kernel commits. Further analysis should compare affected kernel trees and distribution backports to determine whether local builds include the resource-release change.

Mitigation direction

  • Update to a Linux kernel containing the referenced stable fixes.
  • Check your Linux distribution’s security advisory and backport status.
  • Prioritize systems where the lpfc driver is loaded or required.
  • If patching is delayed, follow vendor guidance for risk reduction.

Validation and detection

  • Inventory Linux hosts and kernel versions.
  • Check whether the lpfc driver is present or loaded.
  • Confirm the installed kernel includes the referenced stable fix commits.
  • Review storage host logs for resource exhaustion symptoms.
  • Validate distribution advisories for backported fixes.
Prepared
Confidence
medium
Sources
7

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-49521 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
6Source 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
LinuxLinux4f774513f7b3fe96648b8936f60f835e6ceaa88e, 4f774513f7b3fe96648b8936f60f835e6ceaa88e, 4f774513f7b3fe96648b8936f60f835e6ceaa88e, 4f774513f7b3fe96648b8936f60f835e6ceaa88e, 4f774513f7b3fe96648b8936f60f835e6ceaa88eunaffected
LinuxLinux2.6.31, 0, 5.10.121, 5.15.46, 5.17.14, 5.18.3, 5.19affected
Weakness

CWE details

No CWE listed

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