From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-98386][LOW] scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot [ Upstream Date: Thu, 15 Oct 2026 06:01:27 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-98386 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: 1 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: 53eb96c244d150dfb8cc4b5b0492ab53755f3701 List-Id: CVE: CVE-2026-98386 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot [ Upstream Commit: 53eb96c244d150dfb8cc4b5b0492ab53755f3701 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=53eb96c244d150dfb8cc4b5b0492ab53755f3701 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98386 Analysis date: Thu, 15 Oct 2026 06:01:27 -0400 ActionableScore: 1 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-98386 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98386 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-98386 LOW https://www.kernelcve.org/list/?q=CVE-2026-98386 CHECK WITH IMPACT FROM ORIG NN LOW | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=1 LEGACY=LOW RESULT=DIFF TEMP_DISTANCE_MERGE_SKIP=AEGIS_NO_POSITIVE_SEVERITY_EVIDENCE (independent Legacy and Aegis differ; FINAL: LOW, Aegis: MODERATE_KPANIC) 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-676;CWE-704;CWE-758;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.5';DESCR 'The QLAFX00 request ring is mapped as device I/O memory, but __qla2x00_alloc_iocbs() clears each producer slot with a regular memset(). On ARM64 this operation may use unaligned stores or block zeroing instructions such as DC ZVA that are invalid for device memory, causing a synchronous external abort and potentially a kernel crash. For the CVSS the PR:L reflects that a local user or process with access to storage operations may be able to cause IOCB allocation without having full administrative control of the driver. The base score uses AC:H because exploitation depends on a QLAFX00 adapter, an affected architecture, and a memset implementation that emits incompatible instructions. The paranoid score uses AC:L because after these platform conditions are satisfied, ordinary I/O that allocates an IOCB may reach the faulty operation directly. The demonstrated impact is denial of service only. There is no UAF, OOB access, information leak, or arbitrary write primitive that supports confidentiality or integrity impact. Direct network reachability is not established, although possible triggering through Fibre Channel fabric activity should be checked separately. Automated impact decision path. The original SimpleNet classifier selected LOW. The primary LLM estimated paranoid CVSS 5.5 and the production ActionableScore returned 1 with recommendation Ordinary Moderate. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were final reconciliation stage LOW to LOW because KP specialist did not establish a qualifying panic. The legacy KP specialist has no review artifact for this run. The legacy FD or DH downgrade specialist has no review artifact for this run. Exact triggered rule markers were KPANIC_UNSUPPORTED_REMOVED. The independent weaker Aegis shadow evaluated CVSS 4.8 and ActionableScore 1 with primitive class CLASS_C and manual review RECOMMENDED. Its independently reconciled impact was MODERATE_KPANIC. The models disagreed but the aggregation rules retained the production result. The final reported impact is LOW.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1) MAYBE SIMPLEFIX HARDWARE LINUS KPANIC_UNSUPPORTED_REMOVED - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=1 PrimitiveClass=CLASS_C RealUAF=NO HostAdminRequired=UNKNOWN NamespaceScopedPrivilege=NO ImportantCandidate=NO ManualReview=RECOMMENDED AutoDowngradeAllowed=YES RequiresHostUID0=UNKNOWN AuthorizationDecisionBypass=NO ProtectedResourceImpact=NONE B4PendingReview=NO B4PendingConfirmed=NO 1. ActionableScore * Raw conservative score: 1 * Conservative score: 1 * Raw paranoid score: 1 * Paranoid score: 1 * No floor or cap applied. * Final recommended bucket: **Ordinary Moderate**:: 2. Signal breakdown * +1 Reliable kernel crash / strong DoS. Plain `memset()` on ARM64 Device memory may emit invalid accesses such as DC ZVA and cause a synchronous external abort. * No hardware penalty. QLAFX00 and ARM64 are explicit prerequisites, but the evidence does not establish that the adapter is sufficiently rare to justify minus 2. * No privilege penalty. The complete trigger privilege is unresolved, so host-admin access is not assumed. * No local-unprivileged bonus. Access to storage operations that reliably allocate the affected IOCB is suggested but not established for an ordinary user. * No remote or firmware-mediated bonus. Fibre Channel peer influence over the complete vulnerable operation is not demonstrated. * No corruption bonus. The code writes zeroes to the intended request-ring slot using an invalid accessor. No heap OOB, UAF, arbitrary target, or attacker-controlled payload exists. * No extra Availability point. The synchronous abort and possible kernel crash are the same consequence. * B5-R does not apply. There is no retry-accumulated heap OOB write or later consumption of corrupted heap state. * B3-PENDING does not apply. No shared or file-backed storage is modified. * B4-PENDING does not apply. No authorization decision or mandatory security guard is involved. 3. Reachability analysis The affected system must use a QLAFX00 adapter whose request ring is mapped as Device I/O memory, with an architecture and `memset()` implementation capable of emitting operations invalid for that memory type. ARM64 with block-zeroing or unsuitable unaligned accesses is the documented example. IOCB allocation can occur during normal adapter activity, but the supplied call path does not establish whether an ordinary local user, a Fibre Channel peer, or only a privileged storage-management process can reliably force the specific operation. Existing physical hardware and driver initialization are prerequisites. No namespace-scoped capability participates in the shown path, and no race is required. 4. Primitive and severity interpretation The exact primitive is an invalid CPU access method applied to an intended MMIO request-ring slot. The destination and zero payload are fixed, and the demonstrated consequence is a synchronous external abort with possible host kernel crash. This is CLASS_C crash/DoS behavior, not a kernel heap overwrite or lifetime violation. There is no active structured UAF, repeated release, authorization bypass, disclosure, or useful corruption remaining after excluding the crash. ImportantCandidate is therefore NO. AutoDowngradeAllowed is YES because no unresolved Important-grade primitive is established. Operational severity is ordinary Moderate or Low-like and highly dependent on the affected adapter and architecture combination. 5. One-sentence report phrase Using regular memset on the QLAFX00 MMIO request ring may issue invalid ARM64 Device memory accesses and cause a synchronous external abort or kernel crash, but no independent memory corruption or authorization primitive is established. 6. Manual review recommendation MANUAL CHECK RECOMMENDED Confirm whether an untrusted local storage user or remote Fibre Channel peer can independently force IOCB allocation on an affected ARM64 QLAFX00 system. This reachability question does not alter the currently demonstrated crash-only primitive. 7. Call-site confidence Call-site confidence: medium ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot [ Upstream Commit: 53eb96c244d150dfb8cc4b5b0492ab53755f3701 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=53eb96c244d150dfb8cc4b5b0492ab53755f3701 Changed files: drivers/scsi/qla2xxx/qla_iocb.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=53eb96c244d150dfb8cc4b5b0492ab53755f3701 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98386 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98386 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:H/PR:L/UI:N/S:U/C:N/I:N/A:H 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: unknown Paranoid ActionableScore: 1 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).