[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2024-26807":6},{"stargazers_count":4,"fetched_at":5},7,"2026-06-04T08:53:30.047Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":16,"duplicates":21,"related":22,"reserved_at":9,"published_at":23,"modified_at":24,"state":9,"summary":25,"references_raw":27,"kevs":34,"epss":9,"epss_history":35,"metrics":36,"affected":43},"DEBIAN-CVE-2024-26807","In the Linux kernel, the following vulnerability has been resolved:  Both cadence-quadspi ->runtime_suspend() and ->runtime_resume() implementations start with:  \tstruct cqspi_st *cqspi = dev_get_drvdata(dev); \tstruct 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:  \tstruct cqspi_st *cqspi = dev_get_drvdata(dev);  is correct, but:  \tstruct 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.",null,[],[],[],[14],{"_key":15},"CVE-2024-26807",[17,19],{"_key":18},"DLA-4271-1",{"_key":20},"DSA-5925-1",[],[],"2024-04-04T09:15:09.380Z","2026-04-28T20:27:42.247091Z",{"cisa_kev":26,"cisa_ransomware":26,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":9,"severity_score":9,"severity_version":9,"severity_source":9,"severity_vector":9,"severity_status":9},false,[28],{"url":29,"sources":30,"tags":32},"https://security-tracker.debian.org/tracker/CVE-2024-26807",[31],"osv_debian",[33],"Advisory",[],[],[37],{"source":31,"cvss_v2_0":9,"cvss_v3_0":9,"cvss_v3_1":38,"cvss_v4_0":9},{"baseScore":39,"baseSeverity":9,"vectorString":40,"impactScore":41,"exploitabilityScore":42},5.5,"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",6,4.6,[44,62],{"ecosystem":45,"name":46,"vendor":47,"product":46,"cpe_part":9,"purl_type":48,"purl_namespace":47,"purl_name":46,"source":9,"versions":49},"Debian","linux","debian","deb",[50,54,58,61],{"version":51,"is_range":52,"range_type":53,"version_start":9,"version_start_type":9,"version_end":9,"version_end_type":9,"fixed_in":9},"all",true,"ecosystem",{"version":55,"is_range":52,"range_type":53,"version_start":9,"version_start_type":9,"version_end":56,"version_end_type":57,"fixed_in":9},"lt6_1_140_1","6.1.140-1","excluding",{"version":59,"is_range":52,"range_type":53,"version_start":9,"version_start_type":9,"version_end":60,"version_end_type":57,"fixed_in":9},"lt6_7_9_1","6.7.9-1",{"version":59,"is_range":52,"range_type":53,"version_start":9,"version_start_type":9,"version_end":60,"version_end_type":57,"fixed_in":9},{"ecosystem":45,"name":63,"vendor":47,"product":63,"cpe_part":9,"purl_type":48,"purl_namespace":47,"purl_name":63,"source":9,"versions":64},"linux-6.1",[65],{"version":66,"is_range":52,"range_type":53,"version_start":9,"version_start_type":9,"version_end":67,"version_end_type":57,"fixed_in":9},"lt6_1_140_1~deb11u1","6.1.140-1~deb11u1"]