CVE-2023-53322
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-16

Last updated on: 2025-12-10

Assigner: kernel.org

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-16
Last Modified
2025-12-10
Generated
2026-05-07
AI Q&A
2025-09-16
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 7 associated CPEs
Vendor Product Version / Range
linux linux_kernel to 4.14.322 (exc)
linux linux_kernel From 4.15 (inc) to 4.19.291 (exc)
linux linux_kernel From 4.20 (inc) to 5.4.251 (exc)
linux linux_kernel From 5.5 (inc) to 5.10.188 (exc)
linux linux_kernel From 5.11 (inc) to 5.15.121 (exc)
linux linux_kernel From 5.16 (inc) to 6.1.40 (exc)
linux linux_kernel From 6.2 (inc) to 6.4.5 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-416 The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability in the Linux kernel's qla2xxx SCSI driver involves a use-after-free condition. The function terminate_rport_io can exit before ensuring all IO operations have returned, which can cause system crashes. Specifically, for FCP-2 devices, IOs may hang in hardware because the driver does not immediately tear down the session in firmware when a cable is pulled. When a timeout occurs, terminate_rport_io is called and attempts to free resources, but the cleanup may not complete quickly enough, leaving the driver holding references to freed resources. The fix involves waiting for all IOs to return before freeing resources.


How can this vulnerability impact me? :

This vulnerability can cause system crashes due to use-after-free errors in the Linux kernel's SCSI driver. This can lead to instability, potential data loss, or denial of service on affected systems using the qla2xxx driver with FCP-2 devices, especially when hardware events like cable pulls occur.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart