LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50098: scsi: qla2xxx: Fix crash due to stale SRB access around I/O timeouts

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix crash due to stale SRB access around I/O timeouts Ensure SRB is returned during I/O timeout error escalation. If that is not possible fail the escalation path. Following crash stack was seen: BUG: unable to handle kernel paging request at 0000002f56aa90f8 IP: qla_chk_edif_rx_sa_delete_pending+0x14/0x30 [qla2xxx] Call Trace: ? qla2x00_status_entry+0x19f/0x1c50 [qla2xxx] ? qla2x00_start_sp+0x116/0x1170 [qla2xxx] ? dma_pool_alloc+0x1d6/0x210 ? mempool_alloc+0x54/0x130 ? qla24xx_process_response_queue+0x548/0x12b0 [qla2xxx] ? qla_do_work+0x2d/0x40 [qla2xxx] ? process_one_work+0x14c/0x390

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel crash flaw in the qla2xxx SCSI driver during I/O timeout escalation. The source describes stale SRB access leading to a kernel paging fault. Business impact is likely availability: affected hosts using this driver could crash under relevant storage timeout conditions.

Executive priority

Schedule remediation for exposed storage-dependent Linux hosts. This is not shown as actively exploited, but kernel crashes on storage infrastructure can create outages and recovery workload. Prioritize production systems with qla2xxx usage.

Technical view

The fix ensures an SRB is returned during I/O timeout error escalation, or fails that escalation path when return is not possible. The observed crash path includes qla_chk_edif_rx_sa_delete_pending and qla2x00_status_entry in qla2xxx. No CVSS, CWE, or exploit details are provided.

Likely exposure

Exposure is most likely on Linux systems that use the qla2xxx SCSI driver. The bundle lists Linux as affected and references fixed stable kernel commits. Systems not loading this driver are less likely to be exposed, but confirm against vendor kernel metadata.

Exploitation context

The source bundle marks KEV as false and provides no evidence of active exploitation. The documented condition is a crash around I/O timeout error escalation, not a public remote exploit path. Treat exploitation status as unproven from available sources.

Researcher notes

Evidence is limited to Linux kernel CVE metadata and stable commit references. The vulnerability appears availability-focused from the crash trace. The bundle does not provide CVSS, CWE, exploitability assessment, or distribution-specific affected package ranges.

Mitigation direction

  • Identify systems running affected Linux kernels and using qla2xxx.
  • Review distribution advisories for backported kernel fixes.
  • Upgrade to a vendor kernel containing the referenced stable fixes.
  • Prioritize storage hosts where kernel crashes would affect critical services.

Validation and detection

  • Check whether qla2xxx is loaded on Linux hosts.
  • Compare installed kernel packages against vendor advisories and fixed commits.
  • Review crash logs for qla2xxx stack traces during I/O timeouts.
  • Confirm storage paths recover cleanly after kernel update testing.
Prepared
Confidence
medium
Sources
6

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-50098 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
5Source 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
LinuxLinuxd74595278f4ab192af66d9e60a9087464638beee, d74595278f4ab192af66d9e60a9087464638beee, d74595278f4ab192af66d9e60a9087464638beee, d74595278f4ab192af66d9e60a9087464638beeeunaffected
LinuxLinux4.10, 0, 5.15.61, 5.18.18, 5.19.2, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.