CVE-2024-35809 — PCI/PM: Drain runtime-idle callbacks before driver removal
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Debian Debian Linux, Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (logic error), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Debian | Debian Linux | version 10.0 | Vulnerable | NIST National Vulnerability Database |
| Linux | Linux |
≥ f3ec4f87d607f40497afdb5ac03f11e2ea253d52 and < 9a87375bb586515c0af63d5dcdcd58ec4acf20a6version 2.6.36≥ f3ec4f87d607f40497afdb5ac03f11e2ea253d52 and < 9d5286d4e7f68beab450deddbb6a32edd5ecf4bf≥ f3ec4f87d607f40497afdb5ac03f11e2ea253d52 and < 6347348c6aba52dda0b33296684cbb627bdc6970≥ f3ec4f87d607f40497afdb5ac03f11e2ea253d52 and < d534198311c345e4b062c4b88bb609efb8bd91d5≥ f3ec4f87d607f40497afdb5ac03f11e2ea253d52 and < d86ad8c3e152349454b82f37007ff6ba45f26989≥ f3ec4f87d607f40497afdb5ac03f11e2ea253d52 and < 900b81caf00c89417172afe0e7e49ac4eb110f4b≥ f3ec4f87d607f40497afdb5ac03f11e2ea253d52 and < 7cc94dd36e48879e76ae7a8daea4ff322b7d9674 and 2 more≥ f3ec4f87d607f40497afdb5ac03f11e2ea253d52 and < bbe068b24409ef740657215605284fc7cdddd491≥ f3ec4f87d607f40497afdb5ac03f11e2ea253d52 and < 47d8aafcfe313511a98f165a54d0adceb34e54b1 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel | ≥ 6.8 and < 6.8.3≥ 6.7 and < 6.7.12≥ 6.2 and < 6.6.24≥ 5.16 and < 6.1.84≥ 5.11 and < 5.15.154≥ 5.5 and < 5.10.215≥ 4.20 and < 5.4.274< 4.19.312 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database |
| 5.5 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
| 5.5 | CVSS 3.1 | Medium | — | — | CISA-ADP via CVE Program (cve.org) e CISA ADP |
| 4.7 | CVSS 3.1 | Medium | 1.0 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- SSVC assessment updated
- Record published
- Fix documented
- Affected products added · debian/debian linux, linux/linux kernel
- CVSS changed · 4.7
- Source status changed · → Modified
- Record created in this database
- 2024
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
14 on the record
- git.kernel.org/stable/c/47d8aafcfe313511a98f165a54d0adceb34e54b1
- git.kernel.org/stable/c/9d5286d4e7f68beab450deddbb6a32edd5ecf4bf
- git.kernel.org/stable/c/d534198311c345e4b062c4b88bb609efb8bd91d5
- git.kernel.org/stable/c/bbe068b24409ef740657215605284fc7cdddd491
- git.kernel.org/stable/c/900b81caf00c89417172afe0e7e49ac4eb110f4b
- git.kernel.org/stable/c/6347348c6aba52dda0b33296684cbb627bdc6970
- git.kernel.org/stable/c/9a87375bb586515c0af63d5dcdcd58ec4acf20a6
- git.kernel.org/stable/c/d86ad8c3e152349454b82f37007ff6ba45f26989
- git.kernel.org/stable/c/7cc94dd36e48879e76ae7a8daea4ff322b7d9674
- lists.debian.org/debian-lts-announce/2024/06/msg00017.html
- github.com/advisories/GHSA-3r3f-7rrr-c2h9
- cert-portal.siemens.com/productcert/html/ssa-398330.html
- nvd.nist.gov/vuln/detail/CVE-2024-35809
- lists.debian.org/debian-lts-announce/2024/06/msg00020.html
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 6h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 6h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2024-35809 is "PCI/PM: Drain runtime-idle callbacks before driver removal", rated Medium. It affects Debian Linux (Debian); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.7 describes technical severity. EPSS 0.20% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.