UBUNTU-CVE-2025-68318: Low severity ubuntu/linux-hwe-edge vulnerability

Q: Which systems are exposed to this issue?

Systems using a TH1520 platform with the affected Ubuntu kernel packages are exposed. The listed packages are ubuntu/linux-riscv, ubuntu/linux-realtime, ubuntu/linux-hwe-edge, ubuntu/linux-azure, ubuntu/linux-gcp, ubuntu/linux-azure-fde, ubuntu/linux-aws-5.0, and ubuntu/linux-aws-5.3.

Q: What condition can trigger the failure?

The failure can occur if AXI clocks on the TH1520 are gated. Because the AXI crossbar lacks proper timeout handling, clock gating can cause a bus timeout and system hang.

Q: Is the default reset configuration affected?

The AXI clock gates are ungated by default after a system reset. The issue arises when those clocks are subsequently gated, including through unwanted unused-clock handling.

Q: What mitigation is described if an update cannot be applied immediately?

Avoid gating the TH1520 AXI clocks. The resolved change marks all AXI clock gates as CLK_IS_CRITICAL, including clocks previously using CLK_IGNORE_UNUSED, to prevent unwanted gating.

Published Dec 16, 2025

Updated

In the Linux kernel, the following vulnerability has been resolved: clk: thead: th1520-ap: set all AXI clocks to CLKISCRITICAL The AXI crossbar of TH1520 has no proper timeout handling, which means gating AXI clocks can easily lead to bus timeout and thus system hang. Set all AXI clock gates to CLKISCRITICAL. All these clock gates are ungated by default on system reset. In addition, convert all current CLKIGNOREUNUSED usage to CLKISCRITICAL to prevent unwanted clock gating.

Affected Software

114 affected componentsFixes available

ubuntu/linux-hwe-edge*

ubuntu/linux-aws-5.0*

ubuntu/linux-aws-5.3*

ubuntu/linux-azure*

ubuntu/linux-azure-5.3*

ubuntu/linux-azure-edge*

ubuntu/linux-gcp*

ubuntu/linux-gcp-5.3*

ubuntu/linux-gke-4.15*

ubuntu/linux-gke-5.4*

ubuntu/linux-gkeop-5.4*

ubuntu/linux-hwe*

ubuntu/linux-hwe-edge*

ubuntu/linux-oem*

ubuntu/linux-oracle-5.0*

ubuntu/linux-oracle-5.3*

ubuntu/linux-aws-5.11*

ubuntu/linux-aws-5.13*

ubuntu/linux-aws-5.8*

ubuntu/linux-azure-5.11*

ubuntu/linux-azure-5.13*

ubuntu/linux-azure-5.8*

ubuntu/linux-azure-fde*

ubuntu/linux-gcp-5.11*

ubuntu/linux-gcp-5.13*

ubuntu/linux-gcp-5.8*

ubuntu/linux-gke*

ubuntu/linux-gke-5.15*

ubuntu/linux-gkeop*

ubuntu/linux-gkeop-5.15*

ubuntu/linux-hwe-5.11*

ubuntu/linux-hwe-5.13*

ubuntu/linux-hwe-5.8*

ubuntu/linux-intel-5.13*

ubuntu/linux-oem-5.10*

ubuntu/linux-oem-5.13*

ubuntu/linux-oem-5.6*

ubuntu/linux-oracle-5.11*

ubuntu/linux-oracle-5.13*

ubuntu/linux-oracle-5.8*

ubuntu/linux-raspi2*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.11*

ubuntu/linux-riscv-5.8*

ubuntu/linux-allwinner-5.19*

ubuntu/linux-aws-5.19*

ubuntu/linux-aws-6.2*

ubuntu/linux-aws-6.5*

ubuntu/linux-azure-5.19*

ubuntu/linux-azure-6.2*

ubuntu/linux-azure-6.5*

ubuntu/linux-azure-fde-5.19*

ubuntu/linux-azure-fde-6.2*

ubuntu/linux-gcp-5.19*

ubuntu/linux-gcp-6.2*

ubuntu/linux-gcp-6.5*

ubuntu/linux-hwe-5.19*

ubuntu/linux-hwe-6.2*

ubuntu/linux-hwe-6.5*

ubuntu/linux-intel-iot-realtime*

ubuntu/linux-lowlatency-hwe-5.19*

ubuntu/linux-lowlatency-hwe-6.2*

ubuntu/linux-lowlatency-hwe-6.5*

ubuntu/linux-nvidia-6.2*

ubuntu/linux-nvidia-6.5*

ubuntu/linux-oem-5.17*

ubuntu/linux-oem-6.0*

ubuntu/linux-oem-6.1*

ubuntu/linux-oem-6.5*

ubuntu/linux-oracle-6.5*

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.19*

ubuntu/linux-riscv-6.5*

ubuntu/linux-starfive-5.19*

ubuntu/linux-starfive-6.2*

ubuntu/linux-starfive-6.5*

ubuntu/linux-aws-6.14*

ubuntu/linux-aws-6.17<6.17.0-1007.7~24.04.1

6.17.0-1007.7~24.04.1

ubuntu/linux-azure-6.11*

ubuntu/linux-azure-6.14*

ubuntu/linux-azure-fde-6.14*

ubuntu/linux-azure-fde-6.17*

ubuntu/linux-azure-nvidia-6.14*

ubuntu/linux-gcp-6.11*

ubuntu/linux-gcp-6.14*

ubuntu/linux-gcp-6.17<6.17.0-1008.8~24.04.1

6.17.0-1008.8~24.04.1

ubuntu/linux-hwe-6.11*

ubuntu/linux-hwe-6.14*

ubuntu/linux-lowlatency-hwe-6.11*

ubuntu/linux-nvidia-6.11*

ubuntu/linux-nvidia-6.17<6.17.0-1008.8

6.17.0-1008.8

ubuntu/linux-oem-6.11*

ubuntu/linux-oem-6.14*

ubuntu/linux-oem-6.17<6.17.0-1011.11

6.17.0-1011.11

ubuntu/linux-oem-6.8*

ubuntu/linux-oracle-6.14*

ubuntu/linux-oracle-6.17<6.17.0-1007.7~24.04.1

6.17.0-1007.7~24.04.1

ubuntu/linux-raspi-realtime*

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-6.14*

ubuntu/linux-realtime-6.14*

ubuntu/linux-realtime-6.17<6.17.0-1006.7~24.04.1

6.17.0-1006.7~24.04.1

ubuntu/linux<6.17.0-14.14

6.17.0-14.14

ubuntu/linux-aws<6.17.0-1007.7

6.17.0-1007.7

ubuntu/linux-azure<6.17.0-1008.8

6.17.0-1008.8

ubuntu/linux-azure-fde*

ubuntu/linux-gcp<6.17.0-1007.7

6.17.0-1007.7

ubuntu/linux-oracle<6.17.0-1007.7

6.17.0-1007.7

ubuntu/linux-raspi<6.17.0-1008.8

6.17.0-1008.8

ubuntu/linux-realtime<6.17.0-1006.7

6.17.0-1006.7

ubuntu/linux-riscv<6.17.0-14.14.1

6.17.0-14.14.1

ubuntu/linux-vmware*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade ubuntu/linux-aws-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1007.7~24.04.1
Upgrade
Upgrade ubuntu/linux-gcp-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1008.8~24.04.1
Upgrade
Upgrade ubuntu/linux-nvidia-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1008.8
Upgrade
Upgrade ubuntu/linux-oem-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1011.11
Upgrade
Upgrade ubuntu/linux-oracle-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1007.7~24.04.1
Upgrade
Upgrade ubuntu/linux-realtime-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1006.7~24.04.1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 6.17.0-14.14
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 6.17.0-1007.7
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 6.17.0-1008.8
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 6.17.0-1007.7
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 6.17.0-1007.7
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 6.17.0-1008.8
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 6.17.0-1006.7
Upgrade
Upgrade ubuntu/linux-riscv to a version that resolves this vulnerability.
Fixed in 6.17.0-14.14.1
Configuration
Set all AXI clock gates to CLK_IS_CRITICAL and convert existing CLK_IGNORE_UNUSED usage to CLK_IS_CRITICAL to prevent unwanted clock gating and AXI bus timeouts.
Thead TH1520 AP clock gates CLK_IS_CRITICAL = set for all AXI clock gates

Event History

Dec 16, 2025

CVE Published

via OSV·04:16 PM

Data Sourced

via OSV·04:16 PM

DescriptionSeverityAffected Software

Frequently Asked Questions

Which systems are exposed to this issue?

Systems using a TH1520 platform with the affected Ubuntu kernel packages are exposed. The listed packages are ubuntu/linux-riscv, ubuntu/linux-realtime, ubuntu/linux-hwe-edge, ubuntu/linux-azure, ubuntu/linux-gcp, ubuntu/linux-azure-fde, ubuntu/linux-aws-5.0, and ubuntu/linux-aws-5.3.

What condition can trigger the failure?

The failure can occur if AXI clocks on the TH1520 are gated. Because the AXI crossbar lacks proper timeout handling, clock gating can cause a bus timeout and system hang.

Is the default reset configuration affected?

The AXI clock gates are ungated by default after a system reset. The issue arises when those clocks are subsequently gated, including through unwanted unused-clock handling.

What mitigation is described if an update cannot be applied immediately?

Avoid gating the TH1520 AXI clocks. The resolved change marks all AXI clock gates as CLK_IS_CRITICAL, including clocks previously using CLK_IGNORE_UNUSED, to prevent unwanted gating.

UBUNTU-CVE-2025-68318: Low severity ubuntu/linux-hwe-edge vulnerability

Affected Software

Remediation

Event History

Frequently Asked Questions

Which systems are exposed to this issue?

What condition can trigger the failure?

Is the default reset configuration affected?

What mitigation is described if an update cannot be applied immediately?

Company

Resources

Contact

Frequently Asked Questions

Which systems are exposed to this issue?

What condition can trigger the failure?

Is the default reset configuration affected?

What mitigation is described if an update cannot be applied immediately?