From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-97529][MODERATE REGULAR] scsi: qla2xxx: Validate BSG request_len before reading vendor_cmd[] [ Upstream Date: Fri, 25 Sep 2026 06:56:13 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-97529 X-AL-KERNEL-Priority: MODERATE REGULAR X-AL-KERNEL-Severity: MODERATE REGULAR X-AL-KERNEL-Base-Severity: MODERATE X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 2 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: 740f3458a4798af54aaf8cf63e797d407e8b6d3b List-Id: CVE: CVE-2026-97529 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: scsi: qla2xxx: Validate BSG request_len before reading vendor_cmd[] [ Upstream Commit: 740f3458a4798af54aaf8cf63e797d407e8b6d3b Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=740f3458a4798af54aaf8cf63e797d407e8b6d3b Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97529 Analysis date: Fri, 25 Sep 2026 06:56:13 -0400 ActionableScore: 2 ActionableScore lower bound: unknown 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-97529 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97529 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: MODERATE REGULAR 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-97529 MODERATE https://www.kernelcve.org/list/?q=CVE-2026-97529 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:H/UI:N/S:U/C:L/I:L/A:H';CWE-125;*CWE-20;CWE-1284;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.6';DESCR 'An out of bounds heap read in the qla2xxx FC BSG vendor command path occurs because the driver reads vendor_cmd fields and command specific structures without ensuring that the user supplied request_len covers them. A local caller with CAP_SYS_RAWIO can submit a short FC_BSG_HST_VENDOR request with a matching vendor_id. This can read beyond the memdup_user allocation, select an unintended vendor command, or cause a kernel panic. For the CVSS the PR:H reflects that CAP_SYS_RAWIO is required to access this interface in the normal configuration. The issue is not network reachable and requires a system using a supported qla2xxx Fibre Channel adapter and the BSG device interface. Impact is at least local denial of service through a kernel panic. For the paranoid score limited confidentiality and integrity impact are considered because an out of bounds read can influence vendor command dispatch, but the patch does not establish a controlled write or a reliable privilege escalation primitive.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 2) YES WRITE KASAN OOB INIT HARDWARE LINUS MEMORY DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4 NO NO checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=2 PrimitiveClass=CLASS_C RealUAF=NO HostAdminRequired=UNKNOWN NamespaceScopedPrivilege=UNKNOWN ImportantCandidate=NO ManualReview=RECOMMENDED AutoDowngradeAllowed=YES 1. ActionableScore * Raw conservative score: 2 * Conservative score: 2 * Raw paranoid score: 2 * Paranoid score: 2 * Final recommended bucket: **Ordinary Moderate**:: 2. Signal breakdown * +1 Weak indirect corruption and invalid structured input handling. The driver reads beyond the exact memdup_user allocation and can interpret unintended heap contents as vendor command selectors or command parameters. * +1 Reliable kernel crash or strong DoS concern. The supplied evidence explicitly states that the invalid read can panic the kernel. * +0 Confidentiality. No user visible disclosure path or copy of out of bounds heap contents back to userspace is established. * +0 Integrity. Mis-selection of a vendor command is possible, but attacker control of the out of bounds selector or command parameters is not established. The caller already requires CAP_SYS_RAWIO. * +0 Strong exploitation leverage. No out of bounds write, controlled reclaim, arbitrary read or write, callback control, refcount corruption, or privilege escalation primitive is demonstrated. * +0 Remote reachability. The vulnerable BSG ioctl path is local and no network trigger is established. * +0 Local unprivileged trigger. CAP_SYS_RAWIO is explicitly required by the supplied context. * No privilege penalty was applied. CAP_SYS_RAWIO is a strong privilege requirement, but the supplied context does not prove whether the complete BSG device access chain is restricted to host administrator equivalent privilege or can be delegated. * No hardware or niche subsystem penalty was applied. A qla2xxx Fibre Channel adapter is required, but the supplied evidence does not establish that this requirement is sufficiently rare or inaccessible to justify a negative score. 3. Reachability analysis The trigger is a local FC BSG request sent to a qla2xxx adapter BSG device. The caller must hold CAP_SYS_RAWIO and provide a matching vendor_id with a deliberately short FC_BSG_HST_VENDOR request. The patch does not show the exact capability check, device-node permissions, user namespace behavior, or whether CAP_SYS_RAWIO is evaluated in a namespace that an attacker can fully control. Therefore HostAdminRequired is UNKNOWN and NamespaceScopedPrivilege is UNKNOWN. A supported qla2xxx Fibre Channel adapter, its driver, and an exposed BSG interface are required. This is not a directly network reachable vulnerability. No race, prior attacker-controlled host configuration, or repeated lifetime manipulation is involved. 4. Primitive and severity interpretation The established primitive is an out of bounds heap read from a request buffer allocated by memdup_user using the exact user supplied request_len. The vulnerable reads access vendor_cmd array elements or larger command structures after the transport layer has validated only the fixed fc_bsg_request fields. This is not a UAF, double free, refcount bug, or active object lifetime violation. It is also not an attacker controlled heap overwrite. The demonstrated effects are invalid command interpretation and a possible kernel panic. The possibility that out of bounds data may select a firmware, flash, reset, or management handler warrants review, but the supplied patch does not establish attacker control over the out of bounds values or a useful non crash primitive. The appropriate classification is CLASS_C because the directly demonstrated behavior is invalid state handling and DoS rather than a potentially reusable kernel corruption primitive. ImportantCandidate is NO because no concrete privilege escalation, information disclosure, arbitrary write, security boundary bypass, or controlled memory corruption mechanism is established. AutoDowngradeAllowed is YES because the current evidence supports a constrained privileged local invalid-read and panic scenario. A manual review is still recommended to verify whether any qla2xxx vendor command handler can convert heap-derived selector or parameter values into externally observable disclosure, firmware modification, DMA misuse, or another concrete integrity primitive. 5. One-sentence report phrase A CAP_SYS_RAWIO caller can submit a short qla2xxx FC BSG vendor request that causes out of bounds heap reads, potentially mis-selects a vendor command, and can panic the kernel. 6. Manual review recommendation MANUAL CHECK RECOMMENDED Review the reachable vendor command handlers and BSG capability enforcement, especially firmware, option ROM, reset, loopback, and management paths, to determine whether unintended command dispatch can produce an integrity or disclosure primitive beyond the demonstrated kernel crash. 7. Call-site confidence Call-site confidence: medium ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: scsi: qla2xxx: Validate BSG request_len before reading vendor_cmd[] [ Upstream Commit: 740f3458a4798af54aaf8cf63e797d407e8b6d3b Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=740f3458a4798af54aaf8cf63e797d407e8b6d3b 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=740f3458a4798af54aaf8cf63e797d407e8b6d3b ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-97529 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97529 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:H The Best / paranoid CVSS vector: AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:H The Best / paranoid CVSS score: 5.6 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: unknown 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: MODERATE KPANIC detected for this report: NO Published priority for this report (same as in Subject): MODERATE REGULAR 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).