CVE-2022-50744

scsi: lpfc: Fix hard lockup when reading the rx_monitor from debugfs

N/A
Published: December 24, 2025 at 01:05 PM UTC
Updated: June 17, 2026 at 05:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 5.19.175.15.78 ≤ v < 5.15.865.19.17 ≤ v < 5.206.0.3 ≤ v < 6.0.166.1 ≤ v < 6.1.26.1 ≤ v < 6.2147d397e08a406f5997f8a1c7f747fe546bf839521d65b35169112af9b6f873c8eeab972e60107c22c9b5b8326b953f2f48338a7c889e6af457d146f5.15.785.19.176.0.36.1bd269188ea94e40ab002cad7b0df8f12b8f0de54
Vendor states this is fixed in 2cf66428a2545bb33beb9624124a2377468bb478 (fixed)
Vendor states this is fixed in 39761417ea7b654217d6d9085afbf7c87ba3675d (fixed)
Vendor states this is fixed in c44e50f4a0ec00c2298f31f91bc2c3e9bbd81c7e (fixed)
Vendor states this is fixed in cd542900ee5147028bbe603b238efcab8d720838 (fixed)
Vendor states this is fixed in 5.15.86 (unaffected)
Affected range stops below 5.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.0.16 (unaffected)
Vendor states this is fixed in 6.1 (unaffected)
Vendor states this is fixed in 6.1.2 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card