CVE-2026-89848
Description
In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Quiesce response IRQ before freeing request queue qla2xxx_delete_qpair() deletes the request queue before the response queue. qla25xx_delete_req_que() frees the request queue memory (kfree(req) in qla25xx_free_req_que()), but the response-queue MSI-X is only released later, in qla25xx_free_rsp_que(). In that window the response interrupt can still fire, qla2xxx_msix_rsp_q() queues qpair->q_work, and qla_do_work() -> qla24xx_process_response_queue() dereferences the now-freed rsp->req (LOGINOUT/CT/ELS entries and the status path), a use-after-free. The cancel_work_sync() added for the qpair teardown lives in the response free path, which runs after the request queue is already freed, so it does not protect rsp->req. Release the response-queue interrupt and flush qpair->q_work before deleting the request queue, so no late completion can reach the freed request queue. Clearing have_irq makes the subsequent qla25xx_free_rsp_que() skip its free_irq(), and the firmware queue-delete order (request then response) is preserved; the request-delete mailbox completes on the default vector and is unaffected by dropping the qpair response interrupt early.
How to fix
- Linux Linux730a18768b27582636b5af343069c30809b763a2, be68aef64ab2e633867c4ac946d16644c306fc3d, 0a005dcc5e9bf7b31a45422b10f2765b25161389, 7ac5be2a8609679fc6bbfea881360444a5ce8202, 1486cc18be3e2b4c2a730f4a1b0448d009381b3d, 10e9f05f7fd0a103886a867ec8afe621fe4b906a, 157ca7d1af45f87aa14a286754f19c3f72386988, 505753ec2594c6af09a601f0dd60be7d840c1d2d or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| Linux Linux | d74595278f4ab192af66d9e60a9087464638beee ≤ v < 730a18768b27582636b5af343069c30809b763a2, d74595278f4ab192af66d9e60a9087464638beee ≤ v < be68aef64ab2e633867c4ac946d16644c306fc3d, d74595278f4ab192af66d9e60a9087464638beee ≤ v < 0a005dcc5e9bf7b31a45422b10f2765b25161389, d74595278f4ab192af66d9e60a9087464638beee ≤ v < 7ac5be2a8609679fc6bbfea881360444a5ce8202, d74595278f4ab192af66d9e60a9087464638beee ≤ v < 1486cc18be3e2b4c2a730f4a1b0448d009381b3d, d74595278f4ab192af66d9e60a9087464638beee ≤ v < 10e9f05f7fd0a103886a867ec8afe621fe4b906a, d74595278f4ab192af66d9e60a9087464638beee ≤ v < 157ca7d1af45f87aa14a286754f19c3f72386988, d74595278f4ab192af66d9e60a9087464638beee ≤ v < 505753ec2594c6af09a601f0dd60be7d840c1d2d, 4.10 | 730a18768b27582636b5af343069c30809b763a2, be68aef64ab2e633867c4ac946d16644c306fc3d, 0a005dcc5e9bf7b31a45422b10f2765b25161389, 7ac5be2a8609679fc6bbfea881360444a5ce8202, 1486cc18be3e2b4c2a730f4a1b0448d009381b3d, 10e9f05f7fd0a103886a867ec8afe621fe4b906a, 157ca7d1af45f87aa14a286754f19c3f72386988, 505753ec2594c6af09a601f0dd60be7d840c1d2d |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.