LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49535: scsi: lpfc: Fix null pointer dereference after failing to issue FLOGI and PLOGI

In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix null pointer dereference after failing to issue FLOGI and PLOGI If lpfc_issue_els_flogi() fails and returns non-zero status, the node reference count is decremented to trigger the release of the nodelist structure. However, if there is a prior registration or dev-loss-evt work pending, the node may be released prematurely. When dev-loss-evt completes, the released node is referenced causing a use-after-free null pointer dereference. Similarly, when processing non-zero ELS PLOGI completion status in lpfc_cmpl_els_plogi(), the ndlp flags are checked for a transport registration before triggering node removal. If dev-loss-evt work is pending, the node may be released prematurely and a subsequent call to lpfc_dev_loss_tmo_handler() results in a use after free ndlp dereference. Add test for pending dev-loss before decrementing the node reference count for FLOGI, PLOGI, PRLI, and ADISC handling.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-49535 is a Linux kernel flaw in the lpfc SCSI driver. Under specific failed Fibre Channel login handling, the kernel can reference a node after it was released. The CVSS rating is high because local, low-privileged access could affect confidentiality, integrity, and availability on exposed systems.

Executive priority

Prioritize in normal high-severity kernel patch cycles, especially for storage-connected Linux servers. Escalate if local users, shared hosting, or untrusted workloads can run on affected hosts.

Technical view

The issue is a CWE-416 use-after-free/null pointer dereference in lpfc FLOGI, PLOGI, PRLI, and ADISC handling. Failed ELS operations can decrement a node reference while dev-loss work remains pending, leading later handlers to dereference released node state. Kernel stable commits add pending dev-loss checks before reference count decrement.

Likely exposure

Exposure appears limited to Linux systems running affected kernels with the lpfc SCSI driver path in use. The CVSS vector is local, low complexity, low privileges, no user interaction. Internet-facing exposure is not indicated by the sources.

Exploitation context

The source bundle does not identify public exploit code or active exploitation. KEV is false. Treat this as a local privilege-context kernel memory safety issue rather than a remote network entry point based on the provided CVSS vector.

Researcher notes

The record’s affected-version data is not fully explanatory, so rely on vendor kernel mapping. The core condition is premature lpfc node release while dev-loss work remains pending after failed ELS handling.

Mitigation direction

  • Update affected Linux kernels to builds containing the referenced stable fixes.
  • Check Linux distribution advisories for packaged kernel versions carrying the fix.
  • Prioritize SAN or SCSI hosts where lpfc is present or operationally required.
  • Plan reboots or live-patching according to normal kernel update procedures.

Validation and detection

  • Inventory Linux kernel versions against the affected version data in the CVE record.
  • Check whether the lpfc driver is installed, loaded, or required on each host.
  • Confirm vendor kernel changelogs include the referenced lpfc stable commits.
  • Verify post-update kernel version and retained storage connectivity in maintenance windows.
Prepared
Confidence
medium
Sources
5

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.

cwe · low confidence lookup

CWE-416: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-49535 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2022-49535Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux52edb2caf675684acf2140a125de4774c691fecd, 52edb2caf675684acf2140a125de4774c691fecd, 52edb2caf675684acf2140a125de4774c691fecdunaffected
LinuxLinux5.11, 0, 5.15.181, 5.18.3, 5.19affected
Weakness

CWE details

CWE-416

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

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs