LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50493: scsi: qla2xxx: Fix crash when I/O abort times out

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix crash when I/O abort times out While performing CPU hotplug, a crash with the following stack was seen: Call Trace: qla24xx_process_response_queue+0x42a/0x970 [qla2xxx] qla2x00_start_nvme_mq+0x3a2/0x4b0 [qla2xxx] qla_nvme_post_cmd+0x166/0x240 [qla2xxx] nvme_fc_start_fcp_op.part.0+0x119/0x2e0 [nvme_fc] blk_mq_dispatch_rq_list+0x17b/0x610 __blk_mq_sched_dispatch_requests+0xb0/0x140 blk_mq_sched_dispatch_requests+0x30/0x60 __blk_mq_run_hw_queue+0x35/0x90 __blk_mq_delay_run_hw_queue+0x161/0x180 blk_execute_rq+0xbe/0x160 __nvme_submit_sync_cmd+0x16f/0x220 [nvme_core] nvmf_connect_admin_queue+0x11a/0x170 [nvme_fabrics] nvme_fc_create_association.cold+0x50/0x3dc [nvme_fc] nvme_fc_connect_ctrl_work+0x19/0x30 [nvme_fc] process_one_work+0x1e8/0x3c0 On abort timeout, completion was called without checking if the I/O was already completed. Verify that I/O and abort request are indeed outstanding before attempting completion.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash affected systems during specific storage error-handling conditions. It involves the qla2xxx storage driver completing an I/O abort after the I/O may already be finished. Business impact is most relevant for Linux hosts using this driver in storage-sensitive environments.

Executive priority

Treat as a reliability risk for Linux storage infrastructure rather than an internet-scale emergency. Prioritize patching on production systems where a kernel crash would interrupt critical storage workloads.

Technical view

The flaw is in Linux kernel qla2xxx abort timeout handling. The fix checks that both the I/O and abort request are still outstanding before completing the request. The reported crash occurred during CPU hotplug, with qla2xxx and nvme_fc paths in the stack trace.

Likely exposure

Exposure appears limited to affected Linux kernel versions where qla2xxx is present and used, especially hosts with NVMe-FC or related storage paths shown in the trace. The bundle does not identify remotely exploitable exposure or affected appliances beyond Linux.

Exploitation context

The source bundle does not report active exploitation, public exploit use, or KEV listing. The evidence describes a kernel crash condition observed during CPU hotplug and abort timeout handling, not a weaponized attack path.

Researcher notes

The record lacks CVSS, CWE, and exploitability details. Analysis should focus on code lineage, kernel vendor backports, and whether qla2xxx/NVMe-FC paths are active. Do not assume remote triggerability from the provided evidence.

Mitigation direction

  • Apply a Linux kernel update containing the referenced stable qla2xxx fixes.
  • Check Linux distribution advisories for backported fixes in supported kernels.
  • Prioritize storage-critical Linux hosts using qla2xxx or NVMe-FC paths.
  • If patch timing is constrained, follow vendor guidance for operational risk reduction.

Validation and detection

  • Inventory Linux kernel versions against the affected and fixed versions in the CVE record.
  • Check whether qla2xxx is loaded or used on storage-connected hosts.
  • Review kernel update changelogs for the referenced qla2xxx abort timeout fix.
  • Confirm patched hosts no longer run affected kernel builds after reboot.
Prepared
Confidence
medium
Sources
7

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-50493 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
3Timeline events
0ADP providers
6Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux71c80b75ce8f08c0978ce9a9816b81b5c3ce5e12, 71c80b75ce8f08c0978ce9a9816b81b5c3ce5e12, 71c80b75ce8f08c0978ce9a9816b81b5c3ce5e12, 71c80b75ce8f08c0978ce9a9816b81b5c3ce5e12, 71c80b75ce8f08c0978ce9a9816b81b5c3ce5e12, 457173c8b43ecd3ac48c8ace8d4437a50f7ad77b, b7abcc7df5e131c0b4bf89cb2411c5301ee83d26, 5.3.17, 5.4.4unaffected
LinuxLinux5.5, 0, 5.10.258, 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.