From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-89862][LOW] scsi: qla2xxx: Fix BSG job leak on validate flash image error path Date: Wed, 16 Sep 2026 13:32:39 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-89862 X-AL-KERNEL-Priority: LOW X-AL-KERNEL-Severity: LOW X-AL-KERNEL-Base-Severity: LOW X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 2 X-AL-KERNEL-ActionableScore-Lower: 1 X-AL-KERNEL-Commit: e25241f9fa01fb0c088381a156d84a725b71c1ef List-Id: CVE: CVE-2026-89862 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: scsi: qla2xxx: Fix BSG job leak on validate flash image error path Commit: e25241f9fa01fb0c088381a156d84a725b71c1ef Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e25241f9fa01fb0c088381a156d84a725b71c1ef Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89862 Analysis date: Wed, 16 Sep 2026 13:32:39 -0400 ActionableScore: 2 ActionableScore lower bound: 1 Actionable bucket: Ordinary Moderate Manual review required: NO Summary: No one-sentence report phrase was found. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-89862 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89862 The original announcement does not normally provide a security severity estimate, CVSS assessment, or enough information to determine whether the reported kernel bug represents a practically relevant security issue. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. It combines an autonomous classifier with LLM-assisted technical analysis and a separate ActionableScore mechanism. The purpose of this report is to prioritize Linux kernel CVEs before manual review, identify cases that require prompt investigation, and support automatic closure of issues that are unlikely to have meaningful security impact. Published priority for this report: LOW Manual review required: NO A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-89862 LOW https://www.kernelcve.org/list/?q=CVE-2026-89862 CHECK WITH IMPACT FROM ORIG NN LOW Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';*CWE-772;CWE-404;**CWE-400;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.5';DESCR 'qla28xx_validate_flash_image() can leave an FC BSG job incomplete on the validate flash image error path because the driver returns success while bsg_job_done() is skipped when rval is an error. The FC BSG transport then assumes the driver owns completion, so the request can dangle until timeout and retain block layer resources. For the CVSS the PR:L is used for the paranoid score because some deployments may delegate BSG device access to a service account or storage management role, although typical systems restrict this path to administrators. The issue is not network reachable and requires local access to the BSG control interface. Impact is denial of service through resource retention and possible exhaustion of BSG or block layer resources, with no evidence of UAF, OOB access, information disclosure, or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 2) YES SIMPLEFIX LEAK ERRORPATH HARDWARE LINUS INCREASED_FROM_LOW_BASED_ON_HIGHCVSSSCORE DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4 DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 YES NO checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=2 ActionableScoreLower=1 PrimitiveClass=CLASS_C RealUAF=NO HostAdminRequired=UNKNOWN NamespaceScopedPrivilege=NO ImportantCandidate=NO ManualReview=NO AutoDowngradeAllowed=YES 1. ActionableScore * Raw conservative score: 1 * Conservative score: 1. No floor or cap applied. * Raw paranoid score: 2 * Paranoid score: 2. No floor or cap applied. * Final recommended bucket: **Ordinary Moderate**:: 2. Signal breakdown Positive conservative signals: * +1 Concrete resource or reference retention. The driver returns QLA_SUCCESS while skipping bsg_job_done() on the rval error path, so the FC BSG transport assumes the driver owns completion and the request can dangle until timeout while retaining block layer resources. Positive paranoid signals: * +1 Possible resource exhaustion under repeated triggering. If the error path can be triggered repeatedly before timeout cleanup catches up, BSG or block layer resources may accumulate enough to cause operational DoS. Non-awarded signals: * RealUAF not awarded. The patch establishes an incomplete BSG job completion and resource retention, not use after free. * Concrete repeated release/refcount not awarded. The fixed path changes skipped completion into unconditional completion, but does not show a second put, release, free, or refcount mutation on the same dangling object. * Reliable kernel crash not awarded. The supplied evidence describes dangling requests and resource leakage until timeout, not panic, Oops, or memory corruption. * C/I impact not awarded. No information disclosure, arbitrary write, unauthorized modification, or privilege escalation primitive is established. * Remote reachability not awarded. This is a local FC BSG control path, not a network packet processing path. * Host-admin penalty not applied. Administrative or storage-management access is likely in normal deployments, but the supplied evidence does not positively establish host-admin-equivalent privilege as the only complete trigger path. 3. Reachability analysis The trigger is local access to the FC BSG interface for the qla2xxx adapter and the validate flash image operation. Typical deployments restrict such device-management paths to root, storage administrators, or privileged management services, but the supplied evidence does not prove a mandatory host-admin-equivalent capability check for the complete path. Therefore HostAdminRequired is UNKNOWN rather than YES. NamespaceScopedPrivilege is NO because this is not a network namespace scoped operation. No network reachability is established. No special race is required. The sequence is an ordered error path: validate flash image returns an error in rval, bsg_job_done() is skipped, and the function still returns QLA_SUCCESS to the transport. Prior hardware or driver presence is required in the practical sense because this is qla2xxx Fibre Channel driver code, but the scoring does not apply a rare-hardware penalty from the supplied evidence alone. 4. Primitive and severity interpretation The exact primitive is incomplete request completion causing temporary retention of block layer resources until timeout. This is a resource-management and error-path logic bug, not active structured UAF, fixed stale storage UAF, double free, or repeated lifetime mutation. PrimitiveClass is CLASS_C because the demonstrated behavior is DoS/resource retention without an independently useful corruption primitive. The demonstrated consequence is delayed completion and possible resource pressure. The speculative consequence is broader BSG or block layer exhaustion under sustained repeated triggering, but no kernel memory corruption or privilege escalation path is supported. ImportantCandidate is NO because no Class A primitive, real UAF, repeated release/refcount mutation, authorization bypass, COW ownership violation, or controlled corruption is established. AutoDowngradeAllowed is YES because the issue is a constrained resource leak with no unresolved meaningful exploitation leverage beyond DoS. 5. One-sentence report phrase qla28xx_validate_flash_image() can leave an FC BSG job incomplete on an error path because the driver returns success while skipping bsg_job_done(), allowing the request to retain block layer resources until timeout and potentially causing local DoS through resource exhaustion. 6. Manual review recommendation NO MANUAL CHECK NEEDED Reason: the patch supports a resource-retention DoS only, with no UAF, repeated refcount mutation, memory corruption, information disclosure, authorization bypass, or privilege escalation evidence. 7. Call-site confidence Call-site confidence: high ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: scsi: qla2xxx: Fix BSG job leak on validate flash image error path Commit: e25241f9fa01fb0c088381a156d84a725b71c1ef Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e25241f9fa01fb0c088381a156d84a725b71c1ef Commit description: 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 c2c6822 ("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. Fixes: c2c6822 ("scsi: qla2xxx: Fix bsg_done() causing double free") Cc: stable@vger.kernel.org Signed-off-by: Nilesh Javali Reviewed-by: Hannes Reinecke Link: https://patch.msgid.link/20260723050413.3897522-55-njavali@marvell.com Signed-off-by: Martin K. Petersen (Oracle) Signed-off-by: Greg Kroah-Hartman Changed files: drivers/scsi/qla2xxx/qla_bsg.c Diff excerpt: Not included in this email. See the upstream URL for the full patch. Full patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e25241f9fa01fb0c088381a156d84a725b71c1ef ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-89862 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89862 The original CVE announcement normally does not include a security-level estimate. In particular, it may not contain a CVSS assessment, an impact level, or enough information to determine whether the reported bug is a practically relevant security issue. One purpose of this parallel CVE list is to provide that missing technical and prioritization information. The original goal of the AL-KERNEL project was to prioritize Linux kernel CVE analysis automatically before manual review. The system can also help identify non-security issues that may be suitable for automatic closure. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. The first analysis stage combines an autonomous classifier with additional LLM-based analysis. The autonomous classifier runs locally on a CPU and is based on a backpropagation neural network. Together, these mechanisms produce a technical vulnerability description, identify likely weakness types, estimate CVSS severity, and provide input for ActionableScore. Two CVSS estimates are retained because incomplete kernel vulnerability information often permits more than one defensible interpretation: Conservative CVSS vector: AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 5.5 The conservative vector represents a lower-impact interpretation. The Best/paranoid vector intentionally represents a plausible upper-bound interpretation and should not automatically be treated as demonstrated real-world impact. CVSS may also need to be adjusted for a particular Linux deployment, because actual reachability, privileges, enabled kernel configuration, hardware, namespaces, exposed device nodes, and other environmental conditions can differ significantly between systems. A separate ActionableScore mechanism evaluates practical remediation urgency. Its analysis may include reachability, attack prerequisites, subsystem exposure, memory-corruption characteristics, denial-of-service reliability, and possible confidentiality, integrity, or privilege-escalation impact. Conservative ActionableScore: 1 Paranoid ActionableScore: 2 The final base severity is taken directly from the second tab-separated field of the AL-KERNEL classification result. ActionableScore does not replace or independently override that final AL-KERNEL decision, and if ActionableScore adjusted impact level of ALKERNEL, then you would see self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7. For an AL-KERNEL result of MODERATE, this report uses the following additional presentation split: ActionableScore below 5 -> MODERATE REGULAR ActionableScore 5 or more -> MODERATE 7.0 The distinction between MODERATE REGULAR and MODERATE 7.0 makes it possible to identify Moderate issues that should receive manual analysis and fixes before lower-priority MODERATE REGULAR issues. In many cases, MODERATE REGULAR fixes may wait for a later rebase or routine update. There is one override in which MODERATE REGULAR becomes MODERATE 7.0 even when the ActionableScore is below 5. When the AL-KERNEL result contains the KPANIC flag, a MODERATE result is always presented as MODERATE 7.0. The KPANIC flag selected with few regexps without usage of AI at all, so it helps to detect cases when Kernel Crash happens and similar (to filter False-Negative results from the LLM usage). KPANIC indicates that a reliable kernel crash, kernel panic, or similarly serious kernel availability impact was identified by the classification workflow. AL-KERNEL base severity for this report: LOW KPANIC detected for this report: NO Published priority for this report (same as in Subject): LOW These results are intended to support engineering triage. They are machine-generated estimates, and cases marked for manual review should be validated by a human security engineer before final disposition. For more info read docs linked from here: https://kernelcve.org/ (and you can submit you own patch there to generate such a report for non-existant CVE-id yet). Note that in many cases this AI tool selects higher severity, than real is (means you can expect Importants instead of Moderate 7.0 or Moderates 7.0 instead of regular Moderates). If you see such cases, please use reply email interface to add additional manual analyses info to this particular CVE. And please, please, let me know when you see Lows instead of Importants or Important instead of Low (because particular for such cases I need to tune this AI tool to make it better for this one and next similar). My contact email for such notifications is alexanjelausa@gmail.com (and both send reply to CVE record itself too and see "reply" button below for howto reply).