From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-93814][LOW] spi: core: Abort active target transfer on controller suspend [ Upstream Date: Thu, 24 Sep 2026 14:24:54 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-93814 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: b81ac605763c319ca9928a237818ab4e8ab7bb59 List-Id: CVE: CVE-2026-93814 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: spi: core: Abort active target transfer on controller suspend [ Upstream Commit: b81ac605763c319ca9928a237818ab4e8ab7bb59 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b81ac605763c319ca9928a237818ab4e8ab7bb59 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93814 Analysis date: Thu, 24 Sep 2026 14:24:54 -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-93814 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93814 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-93814 LOW https://www.kernelcve.org/list/?q=CVE-2026-93814 CHECK WITH IMPACT FROM ORIG NN MODERATE Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';*CWE-664;CWE-754;**CWE-400;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'An SPI controller operating in target mode may be suspended while an active target transfer is still in progress. This can leave controller hardware in an inconsistent state and cause a system hang during suspend or a failure to resume correctly. For the CVSS the PR:L value is used for the paranoid score because a restricted service account or delegated power management context may be able to initiate or indirectly cause suspend on some embedded systems. The issue is not network reachable. Impact is denial of service only. No memory corruption, information disclosure, integrity impact, or privilege escalation primitive is indicated by the patch context.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1) YES INIT SIMPLEFIX HARDWARE DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_GUESSCVSS_AND_CIANNH NO NO checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=1 PrimitiveClass=CLASS_C RealUAF=NO HostAdminRequired=UNKNOWN NamespaceScopedPrivilege=UNKNOWN ImportantCandidate=NO ManualReview=NO AutoDowngradeAllowed=YES 1. ActionableScore * Raw conservative score: 1 * Conservative score: 1 * Raw paranoid score: 1 * Paranoid score: 1 * Final recommended bucket: **Ordinary Moderate**:: The conservative and paranoid scores are identical because the patch establishes only a possible controller or system availability failure. There is no supported stronger interpretation involving memory corruption, a security boundary, or attacker-controlled state. 2. Signal breakdown * +1 Reliable kernel or system availability impact: An active SPI target transfer can remain active across controller suspend, leaving hardware in an inconsistent state and potentially causing a suspend hang or failed resume. * +0 Remote reachable: Not established. SPI target traffic is not direct network input. * +0 Local unprivileged trigger: Not established. The supplied context does not show that an ordinary user can configure target mode, start the relevant transfer, and cause suspend. * +0 Firmware mediated external influence: Not awarded. The patch does not establish attacker control of the external SPI peer or controller firmware. * +0 Memory corruption: Not established. There is no UAF, stale dereference, OOB access, invalid free, refcount mutation, DMA overwrite, or ownership violation. * +0 Confidentiality and integrity impact: Not awarded. The described inconsistent hardware state supports availability impact only. * +0 Privilege escalation: Not established. * +0 Hard race penalty: Not applied. This is an ordered suspend lifecycle omission, not a demonstrated timing race. * +0 rare hardware penalty: Not applied. The code is hardware related, but the supplied context does not establish rare or physical only attacker requirements. 3. Reachability analysis The affected path requires an SPI controller operating in target mode, an active target transfer in ctlr->cur_msg, and a system suspend transition before that transfer has been terminated. The supplied patch does not identify who can perform the complete sequence. It does not establish whether SPI target mode is enabled by a host administrator, a restricted embedded service, a local application, firmware, or an external peripheral. It also does not establish whether an attacker can trigger system suspend. HostAdminRequired is therefore UNKNOWN. It would be incorrect to assume host administration is required solely because suspend and SPI controller configuration are commonly privileged. It would also be incorrect to claim below host admin reachability without evidence that the complete controller setup, active transfer, and suspend sequence is available to such an actor. NamespaceScopedPrivilege is UNKNOWN. No namespace based capability or namespace reachable device operation is shown. There is no direct network reachable path. 4. Primitive and severity interpretation The primitive is an invalid controller lifecycle state. The suspend path fails to terminate an active target mode transfer before suspending the SPI controller. The demonstrated consequence is a possible controller inconsistency that can cause a system hang during suspend or failure to resume. This is not a lifetime bug. No object is freed while referenced, no stale object is dereferenced, and no second release or refcount mutation exists. It is not an active structured object corruption case and does not involve fixed stale storage. PrimitiveClass is CLASS_C because the issue is an invalid state and availability problem without an independently useful corruption or authorization primitive. The patch does not support arbitrary read or write, controlled object replacement, callback control, disclosure, integrity violation, privilege escalation, or a security boundary bypass. ImportantCandidate is NO because the patch context shows only a suspend and resume reliability issue. AutoDowngradeAllowed is YES because no unresolved memory corruption, lifetime corruption, ownership violation, or authorization primitive remains. Likely operational severity is Low to ordinary Moderate. The practical impact may be relevant for affected embedded systems using SPI target mode, but it is a DoS and reliability fix rather than a kernel security vulnerability with demonstrated exploitation leverage. 5. One-sentence report phrase An SPI target controller can be suspended while a target transfer remains active, potentially leaving the controller in an inconsistent state and causing a system hang or resume failure. 6. Manual review recommendation NO MANUAL CHECK NEEDED The patch establishes a controller suspend lifecycle omission with availability impact only and does not show a memory corruption, authorization bypass, or attacker reachable security primitive. 7. Call-site confidence Call-site confidence: medium ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: spi: core: Abort active target transfer on controller suspend [ Upstream Commit: b81ac605763c319ca9928a237818ab4e8ab7bb59 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b81ac605763c319ca9928a237818ab4e8ab7bb59 Changed files: drivers/spi/spi.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=b81ac605763c319ca9928a237818ab4e8ab7bb59 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-93814 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93814 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:H/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 4.7 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).