CVE - CVE-2024-35809

CVE-ID
CVE-2024-35809	Learn more at National Vulnerability Database (NVD) • CVSS Severity Rating • Fix Information • Vulnerable Software Versions • SCAP Mappings • CPE Information
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.
References
Note: References are provided for the convenience of the reader to help distinguish between vulnerabilities. The list is not intended to be complete.
MISC:https://git.kernel.org/stable/c/47d8aafcfe313511a98f165a54d0adceb34e54b1 URL:https://git.kernel.org/stable/c/47d8aafcfe313511a98f165a54d0adceb34e54b1 MISC:https://git.kernel.org/stable/c/6347348c6aba52dda0b33296684cbb627bdc6970 URL:https://git.kernel.org/stable/c/6347348c6aba52dda0b33296684cbb627bdc6970 MISC:https://git.kernel.org/stable/c/7cc94dd36e48879e76ae7a8daea4ff322b7d9674 URL:https://git.kernel.org/stable/c/7cc94dd36e48879e76ae7a8daea4ff322b7d9674 MISC:https://git.kernel.org/stable/c/900b81caf00c89417172afe0e7e49ac4eb110f4b URL:https://git.kernel.org/stable/c/900b81caf00c89417172afe0e7e49ac4eb110f4b MISC:https://git.kernel.org/stable/c/9a87375bb586515c0af63d5dcdcd58ec4acf20a6 URL:https://git.kernel.org/stable/c/9a87375bb586515c0af63d5dcdcd58ec4acf20a6 MISC:https://git.kernel.org/stable/c/9d5286d4e7f68beab450deddbb6a32edd5ecf4bf URL:https://git.kernel.org/stable/c/9d5286d4e7f68beab450deddbb6a32edd5ecf4bf MISC:https://git.kernel.org/stable/c/bbe068b24409ef740657215605284fc7cdddd491 URL:https://git.kernel.org/stable/c/bbe068b24409ef740657215605284fc7cdddd491 MISC:https://git.kernel.org/stable/c/d534198311c345e4b062c4b88bb609efb8bd91d5 URL:https://git.kernel.org/stable/c/d534198311c345e4b062c4b88bb609efb8bd91d5 MISC:https://git.kernel.org/stable/c/d86ad8c3e152349454b82f37007ff6ba45f26989 URL:https://git.kernel.org/stable/c/d86ad8c3e152349454b82f37007ff6ba45f26989
Assigning CNA
kernel.org
Date Record Created
20240517	Disclaimer: The record creation date may reflect when the CVE ID was allocated or reserved, and does not necessarily indicate when this vulnerability was discovered, shared with the affected vendor, publicly disclosed, or updated in CVE.
Phase (Legacy)
Assigned (20240517)
Votes (Legacy)

Comments (Legacy)

Proposed (Legacy)
N/A
This is an record on the CVE List, which provides common identifiers for publicly known cybersecurity vulnerabilities.
Search CVE Using Keywords: You can also search by reference using the CVE Reference Maps.
For More Information: CVE Request Web Form (select "Other" from dropdown)