From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-46203][LOW] spi: cadence-quadspi: fix unclocked access on unbind Date: Thu, 28 May 2026 09:37:47 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-46203 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: d67a5311818b3e6481a1e4293c9337ebfee73111 List-Id: CVE: CVE-2026-46203 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: spi: cadence-quadspi: fix unclocked access on unbind Commit: d67a5311818b3e6481a1e4293c9337ebfee73111 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d67a5311818b3e6481a1e4293c9337ebfee73111 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-46203 Analysis date: Thu, 28 May 2026 09:37:47 -0400 ActionableScore: 1 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate / Low-like Manual review required: NO Summary: Cadence QuadSPI driver unbind could access controller registers while clocks were disabled, potentially causing an availability-only bus fault or platform hang on affected hardware. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-46203 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-46203 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-46203 LOW CHECK Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';CWE-665;*CWE-664;CWE-754;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.1';DESCR 'Cadence QuadSPI driver unbind could access controller registers before runtime PM resumed the device, so the access could happen while the controller clocks were disabled. On affected hardware this may cause a bus fault, kernel panic, or platform hang during device removal. For the CVSS the PR:H is used because triggering normally requires administrator level control over driver unbind or platform device management. The issue is not network reachable and is hardware and configuration dependent. Impact is availability only, with no supported memory corruption, information disclosure, or privilege escalation primitive.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1) SKIP CVE-2026-46203 SKIP The Fixes patch not applied yet, so unlikely that actual: 0578a6dbfe7514db7134501cf93acc21cf13e479 YES NO NO unknown MAYBE SIMPLEFIX MEMORY DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=1 ## 1. ActionableScore * Conservative score: 0 * Paranoid score: 1 * Final recommended bucket: **Ordinary Moderate / Low-like**:: ## 2. Signal breakdown Triggered signals: * Availability impact realistic: +1. An unclocked MMIO register access during driver unbind may cause a bus fault, kernel panic, or platform hang on affected hardware. Limiting factors: * Requires admin/root/device-management control: -2. Triggering normally requires driver unbind or platform device removal control. * Hardware/configuration dependent: -1. The impact depends on Cadence QuadSPI hardware, runtime PM state, and SoC behavior on unclocked register access. * No memory corruption. The patch fixes ordering around runtime PM and clocks. * No information disclosure. * No privilege escalation. * No network reachability. ## 3. Reachability analysis The issue is reachable during local driver unbind or device removal. In normal deployments this requires root or equivalent device-management privileges. Containers are relevant only if privileged device management or sysfs driver unbind access is delegated, which is uncommon and already highly privileged. The path is not default reachable by unprivileged local users and is not remotely triggerable. ## 4. Severity interpretation This behaves like a Low / ordinary Moderate stability issue. The realistic impact is availability-only failure during privileged device removal. There is no supported memory corruption, UAF, OOB access, information leak, or LPE primitive. The theoretical platform hang does not change the class because the trigger remains privileged and hardware dependent. ## 5. One-sentence report phrase Cadence QuadSPI driver unbind could access controller registers while clocks were disabled, potentially causing an availability-only bus fault or platform hang on affected hardware. ## 6. Manual review recommendation NO MANUAL CHECK NEEDED This can be auto-closed for security triage unless the deployment treats privileged driver unbind crashes as security relevant. No memory corruption, privilege escalation, information disclosure, or network trigger is supported. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: spi: cadence-quadspi: fix unclocked access on unbind Commit: d67a5311818b3e6481a1e4293c9337ebfee73111 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d67a5311818b3e6481a1e4293c9337ebfee73111 Commit description: Make sure that the controller is runtime resumed before disabling it during driver unbind to avoid an unclocked register access. This issue was flagged by Sashiko when reviewing a controller deregistration fix. Fixes: 0578a6d ("spi: spi-cadence-quadspi: add runtime pm support") Cc: stable@vger.kernel.org # 6.7 Cc: Dhruva Gole Link: https://sashiko.dev/#/patchset/20260414134319.978196-1-johan%40kernel.org?part=2 Signed-off-by: Johan Hovold Link: https://patch.msgid.link/20260421125354.1534871-4-johan@kernel.org Signed-off-by: Mark Brown Signed-off-by: Greg Kroah-Hartman Changed files: drivers/spi/spi-cadence-quadspi.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=d67a5311818b3e6481a1e4293c9337ebfee73111 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-46203 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-46203 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:L The Best / paranoid CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 4.1 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).