CVE-2023-53322: scsi: qla2xxx: Wait for io return on terminate rport
In the Linux kernel, the following vulnerability has been resolved:
scsi: qla2xxx: Wait for io return on terminate rport
System crash due to use after free.
Current code allows terminate_rport_io to exit before making
sure all IOs has returned. For FCP-2 device, IO's can hang
on in HW because driver has not tear down the session in FW at
first sign of cable pull. When dev_loss_tmo timer pops,
terminate_rport_io is called and upper layer is about to
free various resources. Terminate_rport_io trigger qla to do
the final cleanup, but the cleanup might not be fast enough where it
leave qla still holding on to the same resource.
Wait for IO's to return to upper layer before resources are freed.
Security readout for executives and security teams
Plain-English summary
This Linux kernel flaw can crash a system when storage I/O is still active while a remote port is being terminated. It is most relevant to servers using the qla2xxx SCSI/Fibre Channel path. Business impact is primarily host instability and possible disruption to storage-backed workloads.
Executive priority
Treat this as high priority for storage-dependent Linux servers, especially virtualization, database, and backup infrastructure. It is not reported as actively exploited, but a crash in shared storage paths can create material outage risk.
Technical view
The issue is a CWE-416 use-after-free in Linux qla2xxx remote-port teardown. terminate_rport_io could return before outstanding I/O completed, allowing upper layers to free resources while the driver still referenced them after FCP-2 device disruption such as cable loss.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions and using the qla2xxx SCSI/Fibre Channel driver path. Systems without that driver or storage topology are less likely to be reachable through this bug.
Exploitation context
The CVE has CVSS 7.8 with local, low-complexity, low-privilege characteristics. The provided bundle says KEV is false and gives no evidence of active exploitation or public weaponization.
Researcher notes
The root condition is incomplete synchronization during qla2xxx remote-port termination. The fix direction is to wait for I/O return before resources are freed. The provided data does not establish remote exploitability or affected distribution package ranges.
Mitigation direction
Update affected Linux kernels through vendor or stable kernel channels containing the referenced fixes.
Prioritize storage hosts using qla2xxx and Fibre Channel paths.
Check Linux distribution advisories for package-specific fixed versions.
Schedule maintenance because kernel remediation usually requires rebooting affected hosts.
Validation and detection
Inventory Linux hosts with qla2xxx loaded or configured.
Compare running kernel versions against vendor advisories and stable fix availability.
Review storage incident logs for crashes during remote port loss or cable disruption.
Confirm updated hosts boot into the remediated kernel after maintenance.
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.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
1CVSS vectors
3Timeline events
1ADP providers
9Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.