CVE-2024-26605PCI/ASPM: Fix deadlock when enabling ASPM
- 5.5MediumCVSS base score
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: PCI/ASPM: Fix deadlock when enabling ASPM A last minute revert in 6.7-final introduced a potential deadlock when enabling ASPM during probe of Qualcomm PCIe controllers as reported by lockdep: ============================================ WARNING: possible recursive locking detected 6.7.0 #40 Not tainted -------------------------------------------- kworker/u16:5/90 is trying to acquire lock: ffffacfa78ced000 (pci_bus_sem){++++}-{3:3}, at: pcie_aspm_pm_state_change+0x58/0xdc but task is already holding lock: ffffacfa78ced000 (pci_bus_sem){++++}-{3:3}, at: pci_walk_bus+0x34/0xbc other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(pci_bus_sem); lock(pci_bus_sem); *** DEADLOCK *** Call trace: print_deadlock_bug+0x25c/0x348 __lock_acquire+0x10a4/0x2064 lock_acquire+0x1e8/0x318 down_read+0x60/0x184 pcie_aspm_pm_state_change+0x58/0xdc pci_set_full_power_state+0xa8/0x114 pci_set_power_state+0xc4/0x120 qcom_pcie_enable_aspm+0x1c/0x3c [pcie_qcom] pci_walk_bus+0x64/0xbc qcom_pcie_host_post_init_2_7_0+0x28/0x34 [pcie_qcom] The deadlock can easily be reproduced on machines like the Lenovo ThinkPad X13s by adding a delay to increase the race window during asynchronous probe where another thread can take a write lock. Add a new pci_set_power_state_locked() and associated helper functions that can be called with the PCI bus semaphore held to avoid taking the read lock twice.
Timeline
ID reserved
By Linux
- 5 days later
· 5 days later
Published
- 2 years later
· 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected b9c370b61d735a0e5390c42771e7eb21413f7868 – < 0f7908a016c092cfdaa16d785fa5099d867bc1a3
- affected 8cc22ba3f77c59df5f1ac47d62df51efb28cd868 – < b0f4478838be1f1d330061201898fef65bf8fd7c
- affected f93e71aea6c60ebff8adbd8941e678302d377869 – < ef90508574d7af48420bdc5f7b9a4f1cdd26bc70
- affected f93e71aea6c60ebff8adbd8941e678302d377869 – < 1e560864159d002b453da42bd2c13a1805515a20
- affected 1f2f662c8bec75d1311e063efaa9107435cf16c8
- affected 6.1.72 – < 6.1.88
- affected 6.6.11 – < 6.6.29
- affected 5.15.147 – < 5.16
- affected 6.7
- unaffected < 6.7
- unaffected 6.1.88 – ≤ 6.1.*
- unaffected 6.6.29 – ≤ 6.6.*
- unaffected 6.7.5 – ≤ 6.7.*
- unaffected 6.8 – ≤ *
References
References4
- https://git.kernel.org/stable/c/0f7908a016c092cfdaa16d785fa5099d867bc1a3 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/b0f4478838be1f1d330061201898fef65bf8fd7c (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/ef90508574d7af48420bdc5f7b9a4f1cdd26bc70 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/1e560864159d002b453da42bd2c13a1805515a20 (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-23867 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-26605)Record last updated .