CVE-2024-35809PCI/PM: Drain runtime-idle callbacks before driver removal

Description

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.

Timeline

Scores

EPSS (exploitation in 30 days)

0.19% · top 91% of all CVEs (12 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

• Linux · Linux

  • affected f3ec4f87d607f40497afdb5ac03f11e2ea253d52 – < 9a87375bb586515c0af63d5dcdcd58ec4acf20a6
  • affected f3ec4f87d607f40497afdb5ac03f11e2ea253d52 – < 47d8aafcfe313511a98f165a54d0adceb34e54b1
  • affected f3ec4f87d607f40497afdb5ac03f11e2ea253d52 – < bbe068b24409ef740657215605284fc7cdddd491
  • affected f3ec4f87d607f40497afdb5ac03f11e2ea253d52 – < 7cc94dd36e48879e76ae7a8daea4ff322b7d9674
  • affected f3ec4f87d607f40497afdb5ac03f11e2ea253d52 – < 900b81caf00c89417172afe0e7e49ac4eb110f4b
  • affected f3ec4f87d607f40497afdb5ac03f11e2ea253d52 – < d86ad8c3e152349454b82f37007ff6ba45f26989
  • affected f3ec4f87d607f40497afdb5ac03f11e2ea253d52 – < d534198311c345e4b062c4b88bb609efb8bd91d5
  • affected f3ec4f87d607f40497afdb5ac03f11e2ea253d52 – < 6347348c6aba52dda0b33296684cbb627bdc6970
  • affected f3ec4f87d607f40497afdb5ac03f11e2ea253d52 – < 9d5286d4e7f68beab450deddbb6a32edd5ecf4bf

• Linux · Linux

  • affected 2.6.36
  • unaffected < 2.6.36
  • unaffected 4.19.312 – ≤ 4.19.*
  • unaffected 5.4.274 – ≤ 5.4.*
  • unaffected 5.10.215 – ≤ 5.10.*
  • unaffected 5.15.154 – ≤ 5.15.*
  • unaffected 6.1.84 – ≤ 6.1.*
  • unaffected 6.6.24 – ≤ 6.6.*
  • unaffected 6.7.12 – ≤ 6.7.*
  • unaffected 6.8.3 – ≤ 6.8.*
  • unaffected 6.9 – ≤ *

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-35801 (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

[![CVE-2024-35809](https://cveledger.app/badge/CVE-2024-35809.svg)](https://cveledger.app/cve/CVE-2024-35809)

Record last updated 15 Oct 2026, 00:40 UTC.