System hang via lpfc lock-order inversion
Published Feb 26, 2025 · Updated May 11, 2026
Improper locking in the Linux kernel lpfc driver allows local users to hang affected systems during high-volume SCSI I/O. The lpfc_abort_handler takes phba->hbalock before lpfc_cmd->buf_lock while the completion path takes the locks in the opposite order, creating a deadlock. Reaching the flaw requires the lpfc driver and stress I/O with at least 500 virtual ports; the reported consequence is a hard system lockup.
Summary
What happened
Improper locking in the Linux kernel lpfc driver allows local users to hang affected systems during high-volume SCSI I/O. The lpfc_abort_handler takes phba->hbalock before lpfc_cmd->buf_lock while the completion path takes the locks in the opposite order, creating a deadlock. Reaching the flaw requires the lpfc driver and stress I/O with at least 500 virtual ports; the reported consequence is a hard system lockup.
The record
- CVE
- CVE-2022-49536
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.1
- Affected versionversion=c2017260eea2db62e7bb1b7cbb1759f1d11ed067 <03cbbd7c2f5ee288f648f4aeedc765a181188553
- Affected versionversion=c2017260eea2db62e7bb1b7cbb1759f1d11ed067 <0c4eed901285b9cae36a622f32bea3e92490da6c
- Affected versionversion=c2017260eea2db62e7bb1b7cbb1759f1d11ed067 <21c0d469349957b5dc811c41200a2a998996ca8d
- Affected versionversion=c2017260eea2db62e7bb1b7cbb1759f1d11ed067 <7625e81de2164a082810e1f27547d388406da610
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo