Service interruption via preemptible CPU lookup
Published Feb 26, 2025 · Updated May 11, 2026
Improper CPU identification in Linux kernel qla2xxx before 5.18 allows local users to interrupt service during queue-pair creation. qla2xxx_create_qpair calls smp_processor_id() while execution is preemptible, causing the kernel's preemption check to emit a BUG complaint. The path requires the qla2xxx driver and compatible storage hardware; public evidence demonstrates the complaint but does not document a crash.
Summary
What happened
Improper CPU identification in Linux kernel qla2xxx before 5.18 allows local users to interrupt service during queue-pair creation. qla2xxx_create_qpair calls smp_processor_id() while execution is preemptible, causing the kernel's preemption check to emit a BUG complaint. The path requires the qla2xxx driver and compatible storage hardware; public evidence demonstrates the complaint but does not document a crash.
The record
- CVE
- CVE-2022-49155
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- 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=4.13
- Affected versionversion=e326d22af9653dd8eff05d71f0d1bad9174578a3 <1ab81d82fb1db7ec4be4b0d04563513e6d4bcdd5
- Affected versionversion=e326d22af9653dd8eff05d71f0d1bad9174578a3 <43195a0c620761fbb88db04e2475313855b948a4
- Affected versionversion=e326d22af9653dd8eff05d71f0d1bad9174578a3 <8077a7162bc3cf658dd9ff112bc77716c08458c5
- Affected versionversion=e326d22af9653dd8eff05d71f0d1bad9174578a3 <9c33d49ab9f3d8bd7512b3070cd2f07c4a8849d5
- Affected versionversion=e326d22af9653dd8eff05d71f0d1bad9174578a3 <a60447e7d451df42c7bde43af53b34f10f34f469
- Affected versionversion=e326d22af9653dd8eff05d71f0d1bad9174578a3 <a669a22aef0ceff706b885370af74b5a60a8ac85
- Affected versionversion=e326d22af9653dd8eff05d71f0d1bad9174578a3 <f68776f28d9134fa65056e7e63bfc734049730b7
- Affected versionversion=e326d22af9653dd8eff05d71f0d1bad9174578a3 <f97316dd393bc8df1cc2af6295a97b876eecf252
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.
Weakness, pattern, technique
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