# CVE-2026-80523: clk: spacemit: k3: set hdma clock as critical

> A missing critical clock flag in the Spacemit K3 HDMA driver allows the clock to be disabled, causing the Linux system to hang during specific page faults.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-80523, GHSA-xwx3-g3pj-m9qw, UBUNTU-CVE-2026-80523

## What is CVE-2026-80523?

CVE-2026-80523 is a high-severity denial of service vulnerability in Linux, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

clk: spacemit: k3: set hdma clock as critical

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.

## Which versions are affected by CVE-2026-80523?


## How do I fix CVE-2026-80523?

Apply the vendor's patch.

## Is CVE-2026-80523 being exploited?

There is no known exploitation of CVE-2026-80523 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80523 and fix it if it is affected.

What it is: CVE-2026-80523 is a high-severity denial of service vulnerability in Linux, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80523 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80523/ (Markdown: https://insights.sbomify.com/CVE-2026-80523/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80523
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80523
- OSV: https://osv.dev/vulnerability/CVE-2026-80523

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80523/
Summaries are generated and may contain mistakes; the official description above is the record.