CVE-2024-26807
Vulnérabilité élevée dans Linux (Linux)
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.
Gravité et risque d'exploitation
CVE-2024-26807 obtient un score CVSS de 7.8/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.24 %, ce qui la place devant 13.7 % des CVE référencées.
Que faire ?
- Vérifiez si Linux (versions 79acf7fb856eade9c3d0cf00fd34a04bf5c43a1c, 5.10.180, <5.11, <=6.1.*, 6.2.15, 5.15.111, b24f1ecc8fe2ceefc14af02edb1744c246d87bf7, 18cb554e9da81bc4eca653c17a0d65e8b5835c09, 6716203844bc8489af5e5564f0fa31e0c094a7ff, d453f25faf681799d636fe9d6899ad91c45aa11e, 0, 6.7.9, <34e1d5c4407c78de0e3473e1fbf8fb74dbe66d03, 1368dbc0a432acf9fc0dcb23bfe52d32ca4c09ab, 6.8, 6.4, <6.3, <4.20, <=6.6.*, <03f1573c9587029730ca68503f5062105b122f61, <6.4, 2087e85bb66ee3652dafe732bb9b9b896229eafc, <5.5, <5.16, 6.1.140, 4.19.283, e3f9fc9a4f1499cc9e1bad4482d377494e367b3d, <32ce3bb57b6b402de2aec1012511e7ac4e7449dc, 6.1.28, <=*, <=6.7.*, 6.6.21, <6.1.140, 5.4.243, <2c914aac9522f6e93822c18dff233d3e92399c81, 6.3.2) est présent sur votre parc.
- Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
- À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
- Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.