CVE-2025-71299

{"id": "CVE-2025-71299", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.5, "attackVector": "LOCAL", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 1.8}]}, "affected": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "affectedData": [{"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "f1eb4e792bb1ee3dcdffa66f8a83a4867cda2dd3", "lessThan": "08dca4c8099a41a9fa3be128a793387603f73a17", "versionType": "git"}, {"status": "affected", "version": "f1eb4e792bb1ee3dcdffa66f8a83a4867cda2dd3", "lessThan": "dcaa104ad9c860a6dbd5797919e0ec0b1cd5a57a", "versionType": "git"}, {"status": "affected", "version": "f1eb4e792bb1ee3dcdffa66f8a83a4867cda2dd3", "lessThan": "9f0736a4e136a6eb61e0cf530ddc18ab6d816ba3", "versionType": "git"}, {"status": "affected", "version": "7f3c5e0585250097be39736e6b182c5779b7b609", "versionType": "git"}, {"status": "affected", "version": "6.17.11", "lessThan": "6.18", "versionType": "semver"}], "programFiles": ["drivers/spi/spi-cadence-quadspi.c"], "defaultStatus": "unaffected"}, {"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "6.18"}, {"status": "unaffected", "version": "0", "lessThan": "6.18", "versionType": "semver"}, {"status": "unaffected", "version": "6.18.16", "versionType": "semver", "lessThanOrEqual": "6.18.*"}, {"status": "unaffected", "version": "6.19.6", "versionType": "semver", "lessThanOrEqual": "6.19.*"}, {"status": "unaffected", "version": "7.0", "versionType": "original_commit_for_fix", "lessThanOrEqual": "*"}], "programFiles": ["drivers/spi/spi-cadence-quadspi.c"], "defaultStatus": "affected"}]}], "published": "2026-05-08T14:16:31.267", "references": [{"url": "https://git.kernel.org/stable/c/08dca4c8099a41a9fa3be128a793387603f73a17", "tags": ["Patch"], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/9f0736a4e136a6eb61e0cf530ddc18ab6d816ba3", "tags": ["Patch"], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/dcaa104ad9c860a6dbd5797919e0ec0b1cd5a57a", "tags": ["Patch"], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "NVD-CWE-noinfo"}]}], "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't 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't know if runtime PM is active so can't 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's do that."}, {"lang": "es", "value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\nspi: cadence-quadspi: Analizar DT para flashes con el resto del an\u00e1lisis de DT\n\nLa reciente refactorizaci\u00f3n de d\u00f3nde se habilita el PM en tiempo de ejecuci\u00f3n, realizada en el commit f1eb4e792bb1 ('spi: spi-cadence-quadspi: Habilitar pm runtime antes para evitar desequilibrio'), hizo que cuando hacemos un pm_runtime_disable() en las rutas de error de probe() podamos activar una deshabilitaci\u00f3n en tiempo de ejecuci\u00f3n que a su vez resulta en deshabilitaciones de reloj duplicadas. Esto es particularmente probable que ocurra cuando hay una descripci\u00f3n de DT faltante o rota para los flashes conectados al controlador.\n\nAl principio de la funci\u00f3n probe hacemos un pm_runtime_get_noresume() ya que la funci\u00f3n probe deja el dispositivo en un estado encendido, pero en la ruta de error no podemos asumir que el PM est\u00e1 habilitado, por lo que tambi\u00e9n deshabilitamos manualmente todo, incluidos los relojes. Esto significa que cuando el PM en tiempo de ejecuci\u00f3n est\u00e1 activo, tanto este como la funci\u00f3n probe liberan la misma referencia al reloj principal para la IP, lo que activa advertencias del subsistema de reloj:\n\n[ 8.693719] clk:75:7 ya deshabilitado\n[ 8.693791] ADVERTENCIA: CPU: 1 PID: 185 en /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\nAbordar este problema correctamente se complica por el hecho de que no sabemos si el PM en tiempo de ejecuci\u00f3n est\u00e1 activo, por lo que no podemos saber si deshabilitar\u00e1 los relojes o no. Sin embargo, podemos eludir el problema para las descripciones de flash moviendo su an\u00e1lisis a cuando analizamos las propiedades del controlador, lo que tambi\u00e9n nos ahorra hacer una serie de configuraciones que nunca podr\u00e1n ser utilizadas, as\u00ed que hag\u00e1moslo."}], "lastModified": "2026-10-14T13:10:00.187", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "4F94524C-FCFA-40B0-BFBB-176385BE0D5D", "versionEndExcluding": "6.18", "versionStartIncluding": "6.17.11"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "B9F70427-D920-454E-9E11-B6F08300C161", "versionEndExcluding": "6.18.16", "versionStartIncluding": "6.18.1"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "373EEEDA-FAA1-4FB4-B6ED-DB4DD99DBE67", "versionEndExcluding": "6.19.6", "versionStartIncluding": "6.19"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.18:-:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "DCE57113-2223-4308-A0F2-5E6ECFBB3C23"}], "operator": "OR"}]}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}