Vulnerability · Published May 8, 2026 · Assigned by Linux

CVE-2025-71299spi: cadence-quadspi: Parse DT for flashes with the rest of the DT parsing

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 2% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.1%top 98.1% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: spi: cadence-quadspi: Parse DT for flashes with the rest of the DT parsing The recent refactoring of where runtime PM is enabled done in commit f1eb4e792bb1 ("spi: spi-cadence-quadspi: Enable pm runtime earlier to avoid imbalance") made the fact that when we do a pm_runtime_disable() in the error paths of probe() we can trigger a runtime disable which in turn results in duplicate clock disables. This is particularly likely to happen when there is missing or broken DT description for the flashes attached to the controller. Early on in the probe function we do a pm_runtime_get_noresume() since the probe function leaves the device in a powered up state but in the error path we can't assume that PM is enabled so we also manually disable everything, including clocks. This means that when runtime PM is active both it and the probe function release the same reference to the main clock for the IP, triggering warnings from the clock subsystem: [ 8.693719] clk:75:7 already disabled [ 8.693791] WARNING: CPU: 1 PID: 185 at /usr/src/kernel/drivers/clk/clk.c:1188 clk_core_disable+0xa0/0xb ... [ 8.694261] clk_core_disable+0xa0/0xb4 (P) [ 8.694272] clk_disable+0x38/0x60 [ 8.694283] cqspi_probe+0x7c8/0xc5c [spi_cadence_quadspi] [ 8.694309] platform_probe+0x5c/0xa4 Dealing with this issue properly is complicated by the fact that we don't know if runtime PM is active so can't tell if it will disable the clocks or not. We can, however, sidestep the issue for the flash descriptions by moving their parsing to when we parse the controller properties which also save us doing a bunch of setup which can never be used so let's do that.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:14linux6.19.6-1DEBIAN-CVE-2025-71299
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2025-71299
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2025-71299
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2025-71299
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2025-71299
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2025-71299
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2025-71299
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-71299
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-71299
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2025-71299
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2025-71299
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2025-71299

Affected products (as reported)

VendorProductVersions
Linux Linux f1eb4e792bb1ee3dcdffa66f8a83a4867cda2dd3 – before 08dca4c8099a41a9fa3be128a793387603f73a17f1eb4e792bb1ee3dcdffa66f8a83a4867cda2dd3 – before dcaa104ad9c860a6dbd5797919e0ec0b1cd5a57af1eb4e792bb1ee3dcdffa66f8a83a4867cda2dd3 – before 9f0736a4e136a6eb61e0cf530ddc18ab6d816ba37f3c5e0585250097be39736e6b182c5779b7b6096.17.11 – before 6.18
Linux Linux 6.18

References