Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-26807spi: cadence-qspi: fix pointer reference in runtime PM hooks

Description

In the Linux kernel, the following vulnerability has been resolved: Both cadence-quadspi ->runtime_suspend() and ->runtime_resume() implementations start with: struct cqspi_st *cqspi = dev_get_drvdata(dev); struct spi_controller *host = dev_get_drvdata(dev); This obviously cannot be correct, unless "struct cqspi_st" is the first member of " struct spi_controller", or the other way around, but it is not the case. "struct spi_controller" is allocated by devm_spi_alloc_host(), which allocates an extra amount of memory for private data, used to store "struct cqspi_st". The ->probe() function of the cadence-quadspi driver then sets the device drvdata to store the address of the "struct cqspi_st" structure. Therefore: struct cqspi_st *cqspi = dev_get_drvdata(dev); is correct, but: struct spi_controller *host = dev_get_drvdata(dev); is not, as it makes "host" point not to a "struct spi_controller" but to the same "struct cqspi_st" structure as above. This obviously leads to bad things (memory corruption, kernel crashes) directly during ->probe(), as ->probe() enables the device using PM runtime, leading the ->runtime_resume() hook being called, which in turns calls spi_controller_resume() with the wrong pointer. This has at least been reported [0] to cause a kernel crash, but the exact behavior will depend on the memory contents. [0] https://lore.kernel.org/all/20240226121803.5a7r5wkpbbowcxgx@dhruva/ This issue potentially affects all platforms that are currently using the cadence-quadspi driver.

Timeline

  1. ID reserved

    By Linux

  2. · 45 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-26807, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 79acf7fb856eade9c3d0cf00fd34a04bf5c43a1c – < 2c914aac9522f6e93822c18dff233d3e92399c81
    • affected 2087e85bb66ee3652dafe732bb9b9b896229eafc – < 03f1573c9587029730ca68503f5062105b122f61
    • affected 2087e85bb66ee3652dafe732bb9b9b896229eafc – < 34e1d5c4407c78de0e3473e1fbf8fb74dbe66d03
    • affected 2087e85bb66ee3652dafe732bb9b9b896229eafc – < 32ce3bb57b6b402de2aec1012511e7ac4e7449dc
    • affected e3f9fc9a4f1499cc9e1bad4482d377494e367b3d
    • affected 6716203844bc8489af5e5564f0fa31e0c094a7ff
    • affected b24f1ecc8fe2ceefc14af02edb1744c246d87bf7
    • affected d453f25faf681799d636fe9d6899ad91c45aa11e
    • affected 18cb554e9da81bc4eca653c17a0d65e8b5835c09
    • affected 1368dbc0a432acf9fc0dcb23bfe52d32ca4c09ab
    • affected 6.1.28 – < 6.1.140
    • affected 4.19.283 – < 4.20
    • affected 5.4.243 – < 5.5
    • affected 5.10.180 – < 5.11
    • affected 5.15.111 – < 5.16
    • affected 6.2.15 – < 6.3
    • affected 6.3.2 – < 6.4
  • Linux · Linux

    • affected 6.4
    • unaffected < 6.4
    • unaffected 6.1.140 – ≤ 6.1.*
    • unaffected 6.6.21 – ≤ 6.6.*
    • unaffected 6.7.9 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-26807 badge
[![CVE-2024-26807](https://cveledger.app/badge/CVE-2024-26807.svg)](https://cveledger.app/cve/CVE-2024-26807)

Record last updated .