Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

EPSS 0.01% · P3
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2024-26807

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
spi: cadence-qspi: fix pointer reference in runtime PM hooks
Source: NVD (National Vulnerability Database)
Vulnerability 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.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel 存在安全漏洞,该漏洞源于 spi cadence-qspi 中存在指针引用问题,可能会导致内存损坏。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux 79acf7fb856eade9c3d0cf00fd34a04bf5c43a1c ~ 2c914aac9522f6e93822c18dff233d3e92399c81 -
LinuxLinux 6.4 -

II. Public POCs for CVE-2024-26807

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-26807

登录查看更多情报信息。

Same Patch Batch · Linux · 2024-04-04 · 32 CVEs total

CVE-2024-26792btrfs: fix double free of anonymous device after snapshot creation failure
CVE-2024-26809netfilter: nft_set_pipapo: release elements in clone only from destroy path
CVE-2024-26808netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain
CVE-2024-26806spi: cadence-qspi: remove system-wide suspend helper calls from runtime PM hooks
CVE-2024-26805netlink: Fix kernel-infoleak-after-free in __skb_datagram_iter
CVE-2024-26804net: ip_tunnel: prevent perpetual headroom growth
CVE-2024-26803net: veth: clear GRO when clearing XDP even when down
CVE-2024-26802stmmac: Clear variable when destroying workqueue
CVE-2024-26800tls: fix use-after-free on failed backlog decryption
CVE-2024-26801Bluetooth: Avoid potential use-after-free in hci_error_reset
CVE-2024-26799ASoC: qcom: Fix uninitialized pointer dmactl
CVE-2024-26798fbcon: always restore the old font data in fbcon_do_set_font()
CVE-2024-26797drm/amd/display: Prevent potential buffer overflow in map_hw_resources
CVE-2024-26796drivers: perf: ctr_get_width function for legacy is not defined
CVE-2024-26795riscv: Sparse-Memory/vmemmap out-of-bounds fix
CVE-2024-26793gtp: fix use-after-free and null-ptr-deref in gtp_newlink()
CVE-2024-26745powerpc/pseries/iommu: IOMMU table is not initialized for kdump over SR-IOV
CVE-2024-26791btrfs: dev-replace: properly validate device names
CVE-2024-26790dmaengine: fsl-qdma: fix SoC may hang on 16 byte unaligned read
CVE-2024-26789crypto: arm64/neonbs - fix out-of-bounds access on short input

Showing top 20 of 32 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

V. Comments for CVE-2024-26807

No comments yet


Leave a comment