CVE-2026-89862scsi: qla2xxx: Fix BSG job leak on validate flash image error path
- —Not scoredno CVSS score yet
- 0.19%Exploitation in 30 daysEPSS · top 91% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix BSG job leak on validate flash image error path qla28xx_validate_flash_image() returns QLA_SUCCESS (0) unconditionally, telling the FC BSG transport (fc_bsg_host_dispatch()) that the driver owns and will complete the request. But bsg_job_done() is guarded by "if (!rval)", so on the error path (rval == -EINVAL) neither the driver nor the transport completes the job. The request dangles until it times out, leaking block layer resources. Commit c2c68225b145 ("scsi: qla2xxx: Fix bsg_done() causing double free") added the "if (!rval)" guard to a batch of BSG handlers. That is correct for handlers that also return the error code (the transport then completes the job once via fail_host_msg), but this function returns QLA_SUCCESS unconditionally, so the guard turned a correct single completion into a leak. Always call bsg_job_done(): bsg_reply->result is DID_OK and the error is reported in vendor_rsp[0], and since the function returns 0 the transport will not complete the job a second time.
Timeline
ID reserved
By Linux
- 5 days later
· 5 days later
Published
- 33 days later
· 33 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.19% · top 91% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected c2c68225b1456f4d0d393b5a8778d51bb0d5b1d0 – < e25241f9fa01fb0c088381a156d84a725b71c1ef
- affected c2c68225b1456f4d0d393b5a8778d51bb0d5b1d0 – < 0fb52cc632464b0cd07f970341330466d772efe1
- affected 057a5bdc481e58ab853117254867ffb22caf9f6e
- affected f2bbb4db0e4a4fbd5e649c0b5d8733f61da24720
- affected 27ac9679c43a09e54e2d9aae9980ada045b428e0
- affected 74e7458537cd9349cf019862e51491f670871707
- affected 871f6236da96c4a9712b8a29d7f555f767a47e95
- affected 31f33b856d2324d86bcaef295f4d210477a1c018
- affected 708003e1bc857dd014d4c44278d7d77c26f91b1c
- affected 5.10.251 – < 5.11
- affected 5.15.201 – < 5.16
- affected 6.1.164 – < 6.2
- affected 6.6.127 – < 6.7
- affected 6.12.74 – < 6.13
- affected 6.18.13 – < 6.19
- affected 6.19.3 – < 6.20
- affected 7.0
- unaffected < 7.0
- unaffected 7.2.5 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-80462 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-89862)Record last updated .