From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-80523][LOW] clk: spacemit: k3: set hdma clock as critical [ Upstream Date: Wed, 26 Aug 2026 12:57:12 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-80523 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: bb81b608db6342e5adccb6aabe900d739dc7cddb List-Id: CVE: CVE-2026-80523 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: clk: spacemit: k3: set hdma clock as critical [ Upstream Commit: bb81b608db6342e5adccb6aabe900d739dc7cddb Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bb81b608db6342e5adccb6aabe900d739dc7cddb Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80523 Analysis date: Wed, 26 Aug 2026 12:57:12 -0400 ActionableScore: 1 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate / Low-like Manual review required: NO Summary: No one-sentence report phrase was found. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-80523 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80523 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-80523 LOW 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-664;CWE-404;CWE-755;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.5';DESCR 'Spacemit K3 hdma clock controls the internal TCM access path for the X100 RISC-V core. If the clock framework disables this clock because it is not marked critical, later CPU activity such as a vector instruction access that generates a page fault can hang the Linux system. For the CVSS the PR:L because a local user or local process is needed to reach the CPU execution path that can expose the hang, while no elevated administrative privilege is indicated. The issue is not network reachable and is limited to affected Spacemit K3 systems. Impact is denial of service only via system hang, with no evidence of memory corruption, information disclosure, or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1) SKIP CVE-2026-80523 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: url YES NO NO unknown MAYBE SIMPLEFIX LINUS INCREASED_FROM_LOW_BASED_ON_HIGHCVSSSCORE DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5 DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=1 1. ActionableScore * Conservative score: 1 * Paranoid score: 1 * Final recommended bucket: **Ordinary Moderate / Low-like** 2. Signal breakdown * Local unprivileged trigger: +1. A local process may reach the problematic CPU execution path, for example vector instruction access with page fault. * Reliable kernel crash / strong DoS: +1. The described failure mode is a Linux system hang. * Availability impact realistic: +1. The hang is system-wide on the affected platform. * Physical-only or rare hardware-only condition: -2. The issue is specific to Spacemit K3 / X100 RISC-V hardware and the HDMA clock dependency. * No memory corruption signal. The patch only marks a clock as critical and does not indicate UAF, OOB, refcount misuse, stale pointer, or overwrite. * No confidentiality or integrity signal. The impact is limited to availability. 3. Reachability analysis A local user or local workload on an affected Spacemit K3 system can plausibly trigger the hang by reaching CPU behavior that depends on the HDMA clock remaining enabled. The path is not network reachable. Containers or namespaces do not materially change the assessment because the issue is platform and CPU execution related rather than a namespaced kernel API. The vulnerable condition depends on this specific SoC clock topology, so exposure is narrow. 4. Severity interpretation This behaves like a platform-specific local DoS rather than an actionable Moderate or Important kernel vulnerability. Theoretical impact is limited to a system hang. There is no realistic evidence of privilege escalation, memory corruption, information disclosure, or cross-boundary policy bypass. 5. One-sentence report phrase A Spacemit K3 clock configuration bug can allow the HDMA clock needed for the X100 RISC-V TCM access path to be shut off, causing a local system hang when later CPU activity depends on that path. 6. Manual review recommendation NO MANUAL CHECK NEEDED. This is a narrow hardware-specific availability issue with no memory corruption, no network reachability, and no plausible privilege escalation path shown by the patch. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: clk: spacemit: k3: set hdma clock as critical [ Upstream Commit: bb81b608db6342e5adccb6aabe900d739dc7cddb Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bb81b608db6342e5adccb6aabe900d739dc7cddb Changed files: drivers/clk/spacemit/ccu-k3.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=bb81b608db6342e5adccb6aabe900d739dc7cddb ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-80523 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80523 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).