CVE-2026-89848
CVE CVE-2026-89848EUVD EUVD-2026-80448Published 2026-09-16T10:31:22.000ZLast changed 2026-09-16T14:39:16.000ZCVSS 8.1
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux d74595278f4ab192af66d9e60a9087464638beee <7ac5be2a8609679fc6bbfea881360444a5ce8202; d74595278f4ab192af66d9e60a9087464638beee <157ca7d1af45f87aa14a286754f19c3f72386988; patch: 7.2.5; patch: 6.18.51; patch: 0; 4.10; d74595278f4ab192af66d9e60a9087464638beee <10e9f05f7fd0a103886a867ec8afe621fe4b906a; d74595278f4ab192af66d9e60a9087464638beee <505753ec2594c6af09a601f0dd60be7d840c1d2d; d74595278f4ab192af66d9e60a9087464638beee <1486cc18be3e2b4c2a730f4a1b0448d009381b3d; patch: 6.12.110; patch: 7.3-rc1; patch: 6.6.157
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.