CVE-2024-26807: spi: cadence-qspi: fix pointer reference in runtime PM hooks
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 03f1573c9587029730ca68503f5062105b122f61, 2c914aac9522f6e93822c18dff233d3e92399c81, 32ce3bb57b6b402de2aec1012511e7ac4e7449dc.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 03f1573c9587029730ca68503f5062105b122f61, 2c914aac9522f6e93822c18dff233d3e92399c81, 32ce3bb57b6b402de2aec1012511e7ac4e7449dc or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Apr 4, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- CWE-787
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.8
- 2.3 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- e3f9fc9a4f1499cc9e1bad4482d377494e367b3d, 6716203844bc8489af5e5564f0fa31e0c094a7ff, b24f1ecc8fe2ceefc14af02edb1744c246d87bf7, d453f25faf681799d636fe9d6899ad91c45aa11e, 18cb554e9da81bc4eca653c17a0d65e8b5835c09, 1368dbc0a432acf9fc0dcb23bfe52d32ca4c09ab, 6.4affected
- 79acf7fb856eade9c3d0cf00fd34a04bf5c43a1c and later · before 2c914aac9522f6e93822c18dff233d3e92399c81affected · git
- 2087e85bb66ee3652dafe732bb9b9b896229eafc and later · before 03f1573c9587029730ca68503f5062105b122f61affected · git
- 2087e85bb66ee3652dafe732bb9b9b896229eafc and later · before 34e1d5c4407c78de0e3473e1fbf8fb74dbe66d03affected · git
- 2087e85bb66ee3652dafe732bb9b9b896229eafc and later · before 32ce3bb57b6b402de2aec1012511e7ac4e7449dcaffected · git
- 6.1.28 and later · before 6.1.140affected · semver
- 4.19.283 and later · before 4.20affected · semver
- 5.4.243 and later · before 5.5affected · semver
- 5.10.180 and later · before 5.11affected · semver
- 5.15.111 and later · before 5.16affected · semver
Affected versions · NVD (10)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.7 and later · before 6.7.9
- linux linux kernel6.4 and later · before 6.6.21
- linux linux kernel4.19.283
- linux linux kernel5.10.180
- linux linux kernel5.15.111
- linux linux kernel5.4.243
- linux linux kernel6.1.28
- linux linux kernel6.2.15
- linux linux kernel6.3.2
- linux linux kernel6.8
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | linux-6.1 | before 6.1.140-1~deb11u1 | 6.1.140-1~deb11u1 |
| Debian:12 | linux | before 6.1.140-1 | 6.1.140-1 |
| Debian:13 | linux | before 6.7.9-1 | 6.7.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-26804Apr 4, 2024 · net: ip_tunnel: prevent perpetual headroom growth31Monitor
- ← EarlierCVE-2024-26806Apr 4, 2024 · spi: cadence-qspi: remove system-wide suspend helper calls from runtime PM hooks22Monitor
- Later →CVE-2024-26808Apr 4, 2024 · netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 03f1573c9587029730ca68503f5062105b122f61 | Vendor (CNA) |
| Linux Linux | 2c914aac9522f6e93822c18dff233d3e92399c81 | Vendor (CNA) |
| Linux Linux | 32ce3bb57b6b402de2aec1012511e7ac4e7449dc | Vendor (CNA) |
| Linux Linux | 34e1d5c4407c78de0e3473e1fbf8fb74dbe66d03 | Vendor (CNA) |
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | 5.11 | Vendor (CNA) |
| Linux Linux | 5.16 | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 6.1.140 | Vendor (CNA) |
| Linux Linux | 6.3 | Vendor (CNA) |
| Linux Linux | 6.4 | Vendor (CNA) |
| debian:linux | 6.1.140-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.1 | 6.1.140-1~deb11u1 · Debian:11 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0494 · May 16, 2024(Linux Kernel Güncellemesi)
- TR-24-0273 · Apr 5, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.