LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50744: scsi: lpfc: Fix hard lockup when reading the rx_monitor from debugfs

In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix hard lockup when reading the rx_monitor from debugfs During I/O and simultaneous cat of /sys/kernel/debug/lpfc/fnX/rx_monitor, a hard lockup similar to the call trace below may occur. The spin_lock_bh in lpfc_rx_monitor_report is not protecting from timer interrupts as expected, so change the strength of the spin lock to _irq. Kernel panic - not syncing: Hard LOCKUP CPU: 3 PID: 110402 Comm: cat Kdump: loaded exception RIP: native_queued_spin_lock_slowpath+91 [IRQ stack] native_queued_spin_lock_slowpath at ffffffffb814e30b _raw_spin_lock at ffffffffb89a667a lpfc_rx_monitor_record at ffffffffc0a73a36 [lpfc] lpfc_cmf_timer at ffffffffc0abbc67 [lpfc] __hrtimer_run_queues at ffffffffb8184250 hrtimer_interrupt at ffffffffb8184ab0 smp_apic_timer_interrupt at ffffffffb8a026ba apic_timer_interrupt at ffffffffb8a01c4f [End of IRQ stack] apic_timer_interrupt at ffffffffb8a01c4f lpfc_rx_monitor_report at ffffffffc0a73c80 [lpfc] lpfc_rx_monitor_read at ffffffffc0addde1 [lpfc] full_proxy_read at ffffffffb83e7fc3 vfs_read at ffffffffb833fe71 ksys_read at ffffffffb83402af do_syscall_64 at ffffffffb800430b entry_SYSCALL_64_after_hwframe at ffffffffb8a000ad

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-50744 is a Linux kernel availability bug in the lpfc storage driver. Reading a debugfs rx_monitor file while I/O is active can trigger a hard lockup and kernel panic. The business impact is potential host outage, mainly on systems using the lpfc driver and exposing the relevant debugfs interface.

Executive priority

Treat as a targeted availability risk for storage-connected Linux servers, not a broad internet-facing emergency. Prioritize patch validation on production hosts using lpfc because a kernel panic can interrupt workloads and storage operations.

Technical view

The issue is in lpfc_rx_monitor_report locking. spin_lock_bh did not protect against timer interrupts, allowing contention with lpfc_cmf_timer/lpfc_rx_monitor_record and causing a hard lockup. Kernel stable fixes change the locking strength to interrupt-safe locking. The CVE record lists affected Linux versions including 5.15.86, 6.0.16, 6.1, 6.1.2, and 6.2.

Likely exposure

Exposure appears limited to Linux systems using the lpfc SCSI/Fibre Channel driver with debugfs access to /sys/kernel/debug/lpfc/fnX/rx_monitor. Exact exposure depends on vendor kernel backports and whether debugfs is mounted or accessible.

Exploitation context

Sources describe a crash condition during active I/O and simultaneous reading of rx_monitor. No provided source or KEV status indicates active exploitation. Practical triggering likely requires local access sufficient to read the debugfs file on an affected host.

Researcher notes

The public record provides a clear crash trace and upstream stable commit references, but no CVSS, CWE, exploit report, or distro-specific advisory details. Avoid assuming remote reachability or universal Linux exposure; the condition is tied to lpfc, debugfs, and concurrent I/O.

Mitigation direction

  • Update to a vendor-supported kernel containing the referenced stable lpfc fixes.
  • Check Linux distribution advisories for backported fixes before relying on upstream version numbers.
  • Restrict debugfs access on production systems where operationally feasible.
  • Prioritize storage hosts using the lpfc driver and running affected kernel builds.

Validation and detection

  • Inventory systems using the lpfc kernel driver.
  • Determine whether debugfs is mounted and lpfc rx_monitor entries are accessible.
  • Compare running kernels against vendor advisories and referenced stable commits.
  • Confirm updated systems include the lpfc locking fix.
Prepared
Confidence
medium
Sources
6

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-50744 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
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux21d65b35169112af9b6f873c8eeab972e60107c2, 2c9b5b8326b953f2f48338a7c889e6af457d146f, bd269188ea94e40ab002cad7b0df8f12b8f0de54, bd269188ea94e40ab002cad7b0df8f12b8f0de54, 147d397e08a406f5997f8a1c7f747fe546bf8395unaffected
LinuxLinux6.1, 0, 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.