CVE-2024-35809PCI/PM: Drain runtime-idle callbacks before driver removal
Updated under an hour ago ()
Does this affect you?
It affects Linux and 5 other products. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: PCI/PM: Drain runtime-idle callbacks before driver removal A race condition between the .runtime_idle() callback and the .remove() callback in the rtsx_pcr PCI driver leads to a kernel crash due to an unhandled page fault [1]. The problem is that rtsx_pci_runtime_idle() is not expected to be running after pm_runtime_get_sync() has been called, but the latter doesn't really guarantee that. It only guarantees that the suspend and resume callbacks will not be running when it returns. However, if a .runtime_idle() callback is already running when pm_runtime_get_sync() is called, the latter will notice that the runtime PM status of the device is RPM_ACTIVE and it will return right away without waiting for the former to complete. In fact, it cannot wait for .runtime_idle() to complete because it may be called from that callback (it arguably does not make much sense to do that, but it is not strictly prohibited). Thus in general, whoever is providing a .runtime_idle() callback needs to protect it from running in parallel with whatever code runs after pm_runtime_get_sync(). [Note that .runtime_idle() will not start after pm_runtime_get_sync() has returned, but it may continue running then if it has started earlier.] One way to address that race condition is to call pm_runtime_barrier() after pm_runtime_get_sync() (not before it, because a nonzero value of the runtime PM usage counter is necessary to prevent runtime PM callbacks from being invoked) to wait for the .runtime_idle() callback to complete should it be running at that point. A suitable place for doing that is in pci_device_remove() which calls pm_runtime_get_sync() before removing the driver, so it may as well call pm_runtime_barrier() subsequently, which will prevent the race in question from occurring, not just in the rtsx_pcr driver, but in any PCI drivers providing .runtime_idle() callbacks.
- CVSS
- 5.5 MEDIUM (v3.1, CISA ADP)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Modified
- Record last updated
- Oct 15, 2026
- First seen by InfoSec Signals
- Oct 15, 2026
Affected products
Linux Linux linux:linux (from the name) | from f3ec4f87d607f40497afdb5ac03f11e2ea253d52 before 9a87375bb586515c0af63d5dcdcd58ec4acf20a6; from f3ec4f87d607f40497afdb5ac03f11e2ea253d52 before 47d8aafcfe313511a98f165a54d0adceb34e54b1; from f3ec4f87d607f40497afdb5ac03f11e2ea253d52 before bbe068b24409ef740657215605284fc7cdddd491; from f3ec4f87d607f40497afdb5ac03f11e2ea253d52 before 7cc94dd36e48879e76ae7a8daea4ff322b7d9674; from f3ec4f87d607f40497afdb5ac03f11e2ea253d52 before 900b81caf00c89417172afe0e7e49ac4eb110f4b; from f3ec4f87d607f40497afdb5ac03f11e2ea253d52 before d86ad8c3e152349454b82f37007ff6ba45f26989; from f3ec4f87d607f40497afdb5ac03f11e2ea253d52 before d534198311c345e4b062c4b88bb609efb8bd91d5; from f3ec4f87d607f40497afdb5ac03f11e2ea253d52 before 6347348c6aba52dda0b33296684cbb627bdc6970; and 1 more ranges | CNA record |
Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP siemens:simatic_s7_1500_cpu_1518_4_pn_dp_mfp (from the name) | from V3.1.0 before V3.1.5 | CISA ADP |
Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP siemens:simatic_s7_1500_cpu_1518f_4_pn_dp_mfp (from the name) | from V3.1.0 before V3.1.5 | CISA ADP |
Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP siemens:siplus_s7_1500_cpu_1518_4_pn_dp_mfp (from the name) | from V3.1.0 before V3.1.5 | CISA ADP |
debian debian_linux debian:debian_linux | 10.0 | NVD |
linux linux_kernel linux:linux_kernel | before 4.19.312; from 4.20 before 5.4.274; from 5.5 before 5.10.215; from 5.11 before 5.15.154; from 5.16 before 6.1.84; from 6.2 before 6.6.24; from 6.7 before 6.7.12; from 6.8 before 6.8.3 | NVD |
References
- https://git.kernel.org/stable/c/9a87375bb586515c0af63d5dcdcd58ec4acf20a6patch
- https://git.kernel.org/stable/c/47d8aafcfe313511a98f165a54d0adceb34e54b1patch
- https://git.kernel.org/stable/c/bbe068b24409ef740657215605284fc7cdddd491patch
- https://git.kernel.org/stable/c/7cc94dd36e48879e76ae7a8daea4ff322b7d9674patch
- https://git.kernel.org/stable/c/900b81caf00c89417172afe0e7e49ac4eb110f4bpatch
- https://git.kernel.org/stable/c/d86ad8c3e152349454b82f37007ff6ba45f26989patch
- https://git.kernel.org/stable/c/d534198311c345e4b062c4b88bb609efb8bd91d5patch
- https://git.kernel.org/stable/c/6347348c6aba52dda0b33296684cbb627bdc6970patch
- https://git.kernel.org/stable/c/9d5286d4e7f68beab450deddbb6a32edd5ecf4bfpatch
- https://lists.debian.org/debian-lts-announce/2024/06/msg00017.htmlthird-party-advisory
- https://lists.debian.org/debian-lts-announce/2024/06/msg00020.htmlthird-party-advisory
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.