CVE-2026-89862

scsi: qla2xxx: Fix BSG job leak on validate flash image error path

N/A
Published: September 16, 2026 at 10:31 AM UTC
Updated: October 19, 2026 at 09:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

057a5bdc481e58ab853117254867ffb22caf9f6e27ac9679c43a09e54e2d9aae9980ada045b428e031f33b856d2324d86bcaef295f4d210477a1c0185.10.2515.15.20157a5bdc481e58ab853117254867ffb22caf9f6e6.1.1646.12.746.18.136.19.36.6.1277.0708003e1bc857dd014d4c44278d7d77c26f91b1c74e7458537cd9349cf019862e51491f670871707871f6236da96c4a9712b8a29d7f555f767a47e95c2c68225b1456f4d0d393b5a8778d51bb0d5b1d0f2bbb4db0e4a4fbd5e649c0b5d8733f61da24720
Vendor states this is fixed in 0fb52cc632464b0cd07f970341330466d772efe1 (fixed)
Vendor states this is fixed in e25241f9fa01fb0c088381a156d84a725b71c1ef (fixed)
Affected range stops below 5.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.19, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.7, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 7.0 (unaffected)
Vendor states this is fixed in 7.2.5 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card