CVE-2026-80523 (GCVE-0-2026-80523)

Vulnerability from cvelistv5 – Published: 2026-08-26 14:37 – Updated: 2026-08-27 05:01
VLAI
Title
clk: spacemit: k3: set hdma clock as critical
Summary
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.
Assigner
Linux CNA
Impacted products
Vendor Product Version
Linux Linux Affected: e371a77255b837f5d64c9d2520f87e41ea5350b9 , < bb81b608db6342e5adccb6aabe900d739dc7cddb (git)
Affected: e371a77255b837f5d64c9d2520f87e41ea5350b9 , < eb525edd48907795c0d4e498ff57ad168070b289 (git)
Create a notification for this product.
Linux Linux Affected: 7.0
Unaffected: 0 , < 7.0 (semver)
Unaffected: 7.1.10 , ≤ 7.1.* (semver)
Unaffected: 7.2 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/clk/spacemit/ccu-k3.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "bb81b608db6342e5adccb6aabe900d739dc7cddb",
              "status": "affected",
              "version": "e371a77255b837f5d64c9d2520f87e41ea5350b9",
              "versionType": "git"
            },
            {
              "lessThan": "eb525edd48907795c0d4e498ff57ad168070b289",
              "status": "affected",
              "version": "e371a77255b837f5d64c9d2520f87e41ea5350b9",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/clk/spacemit/ccu-k3.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "7.0"
            },
            {
              "lessThan": "7.0",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.1.*",
              "status": "unaffected",
              "version": "7.1.10",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1.10",
                  "versionStartIncluding": "7.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "versionStartIncluding": "7.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nclk: spacemit: k3: set hdma clock as critical\n\nHDMA clock is responsible for the internal TCM access path of X100 RISC-V\ncore, so set the clock flag as critical to prevent it from being shut off,\notherwise the Linux system will hang, for example in the case of a vector\ninstruction access generates a page fault."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.1,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - 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.\nAC:L - 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.\nPR:N - 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.\nUI:N - 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.\nS:C - 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.\nC:N - 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.\nI:N - 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.\nA:H - 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."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-27T05:01:19.881Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/bb81b608db6342e5adccb6aabe900d739dc7cddb"
        },
        {
          "url": "https://git.kernel.org/stable/c/eb525edd48907795c0d4e498ff57ad168070b289"
        }
      ],
      "title": "clk: spacemit: k3: set hdma clock as critical",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-80523",
    "datePublished": "2026-08-26T14:37:03.779Z",
    "dateReserved": "2026-08-26T14:34:25.763Z",
    "dateUpdated": "2026-08-27T05:01:19.881Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-80523",
      "date": "2026-11-19",
      "epss": "0.00126",
      "percentile": "0.02329"
    },
    "redhat_vex": {
      "aggregate_severity": "Low",
      "current_release_date": "2026-11-07T10:42:39+00:00",
      "cve": "CVE-2026-80523",
      "id": "CVE-2026-80523",
      "initial_release_date": "2026-08-26T00:00:00+00:00",
      "product_status:known_affected": "1",
      "product_status:known_not_affected": "199",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: clk: spacemit: k3: set hdma clock as critical",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-80523.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.