CVE-2026-97536
Last modified
CVE-2026-97536 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix use-after-free of qpair work on queue teardown The response queue MSI-X handler qla2xxx_msix_rsp_q() schedules qla_do_work() via queue_work(ha->wq, &qpair->q_work). qla_do_work() dereferences the qpair (vha, rsp) and takes qpair->qp_lock. During teardown, qla2xxx_delete_qpair() deletes the response queue, which calls free_irq() in qla25xx_free_rsp_que(), and then frees the queue and the qpair.
Description
In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix use-after-free of qpair work on queue teardown The response queue MSI-X handler qla2xxx_msix_rsp_q() schedules qla_do_work() via queue_work(ha->wq, &qpair->q_work). qla_do_work() dereferences the qpair (vha, rsp) and takes qpair->qp_lock. During teardown, qla2xxx_delete_qpair() deletes the response queue, which calls free_irq() in qla25xx_free_rsp_que(), and then frees the queue and the qpair. free_irq() waits for running hardirq handlers but does not cancel work already placed on ha->wq. A still-pending q_work then runs qla_do_work() against the freed qpair and response queue, causing a use-after-free. This is especially likely during full adapter teardown, where destroy_workqueue(ha->wq) forces pending work to run after the queue pairs have been freed. Flush the work item with cancel_work_sync() in qla25xx_free_rsp_que() after free_irq() has released the interrupt (so no new work can be queued) and before the response queue and qpair memory are freed (so the flushed handler still sees valid memory). Guard on rsp->qpair and ha->wq to match the INIT_WORK() condition and avoid operating on an uninitialized work_struct.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 68ca949cdb04b4dc71451a999148fbc5f187a220, < 1710a69fd74d0b4bdfcc57c3309b1c4057f70d85; >= 68ca949cdb04b4dc71451a999148fbc5f187a220, < f1f4d1cb93eeeb250eac9405121933e268eefbd3; >= 68ca949cdb04b4dc71451a999148fbc5f187a220, < 19788a55cab61d78e33e0914a5a31d27843e8a4a |
| Linux | Linux | 2.6.31 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-97536?
How severe is CVE-2026-97536?
How do I fix CVE-2026-97536?
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-97530In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97531In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-97532In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97533In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97534In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97535In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97537In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97538In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97539In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9754An authenticated user with the read role may read limited am…7.1
- CVE-2026-97540In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97541In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-97536?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
