CVE-2021-46963: scsi: qla2xxx: Fix crash in qla2xxx_mqueuecommand()
In the Linux kernel, the following vulnerability has been resolved:
scsi: qla2xxx: Fix crash in qla2xxx_mqueuecommand()
RIP: 0010:kmem_cache_free+0xfa/0x1b0
Call Trace:
qla2xxx_mqueuecommand+0x2b5/0x2c0 [qla2xxx]
scsi_queue_rq+0x5e2/0xa40
__blk_mq_try_issue_directly+0x128/0x1d0
blk_mq_request_issue_directly+0x4e/0xb0
Fix incorrect call to free srb in qla2xxx_mqueuecommand(), as srb is now
allocated by upper layers. This fixes smatch warning of srb unintended
free.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel storage-driver crash bug. Systems using the qla2xxx SCSI/Fibre Channel driver could crash when handling queued commands because the driver frees memory it should not own. Business impact is mainly availability risk for affected storage-connected servers.
Executive priority
Prioritize normal patch-cycle remediation for servers dependent on qla2xxx-backed storage. Escalate if affected hosts support critical storage paths or have shown related kernel crashes.
Technical view
The kernel qla2xxx driver incorrectly frees an srb in qla2xxx_mqueuecommand(), although that object is allocated by upper layers. The recorded failure path reaches kmem_cache_free(), with call trace through qla2xxx_mqueuecommand(), scsi_queue_rq(), and blk-mq request issuance.
Likely exposure
Exposure appears limited to Linux systems running affected kernel builds with the qla2xxx driver in use, typically servers using compatible Fibre Channel storage adapters. Systems without this driver or hardware are unlikely to be exposed.
Exploitation context
The source bundle does not show KEV listing, public active exploitation, exploit code, or a CVSS score. The available evidence supports a crash/availability issue, not remote compromise. Trigger conditions are not fully described in the supplied sources.
Researcher notes
The record names several upstream stable commits and affected Linux versions, but provides no CVSS, CWE, or detailed trigger path. Analysis should stay focused on memory ownership in qla2xxx_mqueuecommand() and operational availability impact.
Mitigation direction
Update to a vendor-supported kernel containing the qla2xxx fixes.
Follow Linux distribution advisories for exact fixed package versions.
Plan reboots for storage hosts where kernel updates are required.
If patching is delayed, reduce dependency on affected qla2xxx paths where feasible.
Validation and detection
Inventory Linux kernel versions on storage-connected servers.
Confirm whether the qla2xxx driver is present or loaded.
Identify hosts using compatible Fibre Channel storage adapters.
Check kernel crash logs for qla2xxx_mqueuecommand or kmem_cache_free traces.
Map deployed kernels against vendor fixes or listed stable commits.
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-2021-46963 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.