Look up another CVE · open CVE-2026-80523 in the interactive tracker
CVE-2026-80523
clk: spacemit: k3: set hdma clock as critical
Published 2026-08-26 (2 months ago) by the Linux kernel CNA. Subsystem drivers/clk. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-80523 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| Debian 14forky | fixed | 7.1.10-1 | Update the kernel and reboot. Fixed in 7.1.10-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.10-1 | Update the kernel and reboot. Fixed in 7.1.10-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
HDMA clock is responsible for the internal TCM access path of X100 RISC-V core, so set the clock flag as critical to prevent it from being shut off, otherwise the Linux system will hang, for example in the case of a vector instruction access generates a page fault.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/clk/spacemit/ccu-k3.c
- What this is
- COMMON CLK FRAMEWORKMAINTAINERS section matched on drivers/clk/ · linux-clk@vger.kernel.org · Maintained
Check it on the machine
grep -w CONFIG_SPACEMIT_K3_CCU /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed. The build rule could not be established for 2 releases, so nothing is claimed about those.
- bookworm, trixie?
- forky, sidYnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, s390x/s390x
- ?
- not established - no Makefile entry for the affected file
- Y
- built in where it is built at all; some flavours do not build it
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
- Build switch
- CONFIG_SPACEMIT_K3_CCU
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-08-26 (2 months ago)source
- CVSS
- 7.1 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.16%, higher than 4.8% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/clk
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 7.0 | 7.1.10 | bb81b608db63 |
| 7.0 | 7.2 | eb525edd4890 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- Exploitation requires local code execution on a SpacemiT K3 host to trigger RISC-V vector page faults through normal userspace memory access; the hdma_clk gate in drivers/clk/spacemit/ccu-k3.c is not reachable from network packets, Bluetooth, or physical USB interfaces.
- AC:LAttack complexity, low
- On vulnerable K3 kernels the hdma_clk is deterministically disabled at boot by clk_disable_unused() because no driver claims CLK_DCIU_HDMA, and an unprivileged process can reliably hang the system with standard RVV workloads that fault on demand-paged mappings.
- PR:NPrivileges required, none
- Triggering the hang needs only an unprivileged local process executing vector instructions that cause page faults (mmap/mprotect/stack growth); no CAP_SYS_ADMIN, init-namespace root, or user-namespace-only capabilities are required to reach the fault handler.
- UI:NUser interaction, none
- No victim interaction is required beyond the attacker running their own vector workload on the affected K3 system; the boot-time clock gating is automatic and the page fault is self-induced.
- S:CScope, changed
- On multi-tenant K3 edge, automotive, or containerized deployments, an unprivileged process in one container or application context can hang the shared kernel, denying availability to all other tenants and host services on the same SoC.
- C:NConfidentiality impact, none
- The failure mode is a hardware-level system hang when TCM access stalls with HDMA clock gated; there is no out-of-bounds read, use-after-free, or information disclosure primitive in the bug or its documented trigger path.
- I:NIntegrity impact, none
- No kernel or user data is modified; impact is limited to freezing the system when vector page-fault handling cannot complete TCM accesses after hdma_clk was incorrectly shut off by the clock framework.
- A:HAvailability impact, high
- The commit and reporter confirm the Linux system hangs (hard lockup requiring reset) when vector instruction accesses generate page faults while the HDMA clock providing the X100 core TCM access path has been gated off.