CVE-2026-89848
Last modified
CVE-2026-89848 is a high-severity vulnerability rated 8.1/10 on the CVSS scale. 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().
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= d74595278f4ab192af66d9e60a9087464638beee, < 7ac5be2a8609679fc6bbfea881360444a5ce8202; >= d74595278f4ab192af66d9e60a9087464638beee, < 1486cc18be3e2b4c2a730f4a1b0448d009381b3d; >= d74595278f4ab192af66d9e60a9087464638beee, < 10e9f05f7fd0a103886a867ec8afe621fe4b906a; >= d74595278f4ab192af66d9e60a9087464638beee, < 157ca7d1af45f87aa14a286754f19c3f72386988; >= d74595278f4ab192af66d9e60a9087464638beee, < 505753ec2594c6af09a601f0dd60be7d840c1d2d |
| Linux | Linux | 4.10 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-89848?
How severe is CVE-2026-89848?
How do I fix CVE-2026-89848?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-89842In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89843In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89844In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-89845In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89846In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-89847In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-89849In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-8985Autel Maxi Charger Single firmware through V1.03.51 is vulne…9.8
- CVE-2026-89850In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89851In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89852In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89853In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-89848?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
