CVE-2025-71299 (GCVE-0-2025-71299)

Vulnerability from cvelistv5 – Published: 2026-05-08 13:11 – Updated: 2026-05-09 04:09
VLAI?
Title
spi: cadence-quadspi: Parse DT for flashes with the rest of the DT parsing
Summary
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.
Severity ?
No CVSS data available.
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: f1eb4e792bb1ee3dcdffa66f8a83a4867cda2dd3 , < 08dca4c8099a41a9fa3be128a793387603f73a17 (git)
Affected: f1eb4e792bb1ee3dcdffa66f8a83a4867cda2dd3 , < dcaa104ad9c860a6dbd5797919e0ec0b1cd5a57a (git)
Affected: f1eb4e792bb1ee3dcdffa66f8a83a4867cda2dd3 , < 9f0736a4e136a6eb61e0cf530ddc18ab6d816ba3 (git)
Affected: 7f3c5e0585250097be39736e6b182c5779b7b609 (git)
Create a notification for this product.
    Linux Linux Affected: 6.18
Unaffected: 0 , < 6.18 (semver)
Unaffected: 6.18.16 , ≤ 6.18.* (semver)
Unaffected: 6.19.6 , ≤ 6.19.* (semver)
Unaffected: 7.0 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/spi/spi-cadence-quadspi.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "08dca4c8099a41a9fa3be128a793387603f73a17",
              "status": "affected",
              "version": "f1eb4e792bb1ee3dcdffa66f8a83a4867cda2dd3",
              "versionType": "git"
            },
            {
              "lessThan": "dcaa104ad9c860a6dbd5797919e0ec0b1cd5a57a",
              "status": "affected",
              "version": "f1eb4e792bb1ee3dcdffa66f8a83a4867cda2dd3",
              "versionType": "git"
            },
            {
              "lessThan": "9f0736a4e136a6eb61e0cf530ddc18ab6d816ba3",
              "status": "affected",
              "version": "f1eb4e792bb1ee3dcdffa66f8a83a4867cda2dd3",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "7f3c5e0585250097be39736e6b182c5779b7b609",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/spi/spi-cadence-quadspi.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.18"
            },
            {
              "lessThan": "6.18",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.16",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.19.*",
              "status": "unaffected",
              "version": "6.19.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.0",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.16",
                  "versionStartIncluding": "6.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.19.6",
                  "versionStartIncluding": "6.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0",
                  "versionStartIncluding": "6.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionStartIncluding": "6.17.11",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nspi: cadence-quadspi: Parse DT for flashes with the rest of the DT parsing\n\nThe recent refactoring of where runtime PM is enabled done in commit\nf1eb4e792bb1 (\"spi: spi-cadence-quadspi: Enable pm runtime earlier to\navoid imbalance\") made the fact that when we do a pm_runtime_disable()\nin the error paths of probe() we can trigger a runtime disable which in\nturn results in duplicate clock disables.  This is particularly likely\nto happen when there is missing or broken DT description for the flashes\nattached to the controller.\n\nEarly on in the probe function we do a pm_runtime_get_noresume() since\nthe probe function leaves the device in a powered up state but in the\nerror path we can\u0027t assume that PM is enabled so we also manually\ndisable everything, including clocks. This means that when runtime PM is\nactive both it and the probe function release the same reference to the\nmain clock for the IP, triggering warnings from the clock subsystem:\n\n[    8.693719] clk:75:7 already disabled\n[    8.693791] WARNING: CPU: 1 PID: 185 at /usr/src/kernel/drivers/clk/clk.c:1188 clk_core_disable+0xa0/0xb\n...\n[    8.694261]  clk_core_disable+0xa0/0xb4 (P)\n[    8.694272]  clk_disable+0x38/0x60\n[    8.694283]  cqspi_probe+0x7c8/0xc5c [spi_cadence_quadspi]\n[    8.694309]  platform_probe+0x5c/0xa4\n\nDealing with this issue properly is complicated by the fact that we\ndon\u0027t know if runtime PM is active so can\u0027t tell if it will disable the\nclocks or not.  We can, however, sidestep the issue for the flash\ndescriptions by moving their parsing to when we parse the controller\nproperties which also save us doing a bunch of setup which can never be\nused so let\u0027s do that."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-09T04:09:51.835Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/08dca4c8099a41a9fa3be128a793387603f73a17"
        },
        {
          "url": "https://git.kernel.org/stable/c/dcaa104ad9c860a6dbd5797919e0ec0b1cd5a57a"
        },
        {
          "url": "https://git.kernel.org/stable/c/9f0736a4e136a6eb61e0cf530ddc18ab6d816ba3"
        }
      ],
      "title": "spi: cadence-quadspi: Parse DT for flashes with the rest of the DT parsing",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-71299",
    "datePublished": "2026-05-08T13:11:10.518Z",
    "dateReserved": "2026-05-06T11:31:45.510Z",
    "dateUpdated": "2026-05-09T04:09:51.835Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2025-71299\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-05-08T14:16:31.267\",\"lastModified\":\"2026-05-08T14:16:31.267\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nspi: cadence-quadspi: Parse DT for flashes with the rest of the DT parsing\\n\\nThe recent refactoring of where runtime PM is enabled done in commit\\nf1eb4e792bb1 (\\\"spi: spi-cadence-quadspi: Enable pm runtime earlier to\\navoid imbalance\\\") made the fact that when we do a pm_runtime_disable()\\nin the error paths of probe() we can trigger a runtime disable which in\\nturn results in duplicate clock disables.  This is particularly likely\\nto happen when there is missing or broken DT description for the flashes\\nattached to the controller.\\n\\nEarly on in the probe function we do a pm_runtime_get_noresume() since\\nthe probe function leaves the device in a powered up state but in the\\nerror path we can\u0027t assume that PM is enabled so we also manually\\ndisable everything, including clocks. This means that when runtime PM is\\nactive both it and the probe function release the same reference to the\\nmain clock for the IP, triggering warnings from the clock subsystem:\\n\\n[    8.693719] clk:75:7 already disabled\\n[    8.693791] WARNING: CPU: 1 PID: 185 at /usr/src/kernel/drivers/clk/clk.c:1188 clk_core_disable+0xa0/0xb\\n...\\n[    8.694261]  clk_core_disable+0xa0/0xb4 (P)\\n[    8.694272]  clk_disable+0x38/0x60\\n[    8.694283]  cqspi_probe+0x7c8/0xc5c [spi_cadence_quadspi]\\n[    8.694309]  platform_probe+0x5c/0xa4\\n\\nDealing with this issue properly is complicated by the fact that we\\ndon\u0027t know if runtime PM is active so can\u0027t tell if it will disable the\\nclocks or not.  We can, however, sidestep the issue for the flash\\ndescriptions by moving their parsing to when we parse the controller\\nproperties which also save us doing a bunch of setup which can never be\\nused so let\u0027s do that.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/08dca4c8099a41a9fa3be128a793387603f73a17\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/9f0736a4e136a6eb61e0cf530ddc18ab6d816ba3\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/dcaa104ad9c860a6dbd5797919e0ec0b1cd5a57a\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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.



Detection rules are retrieved from Rulezet.