Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

EPSS 0.01% · P0
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2024-35809

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
PCI/PM: Drain runtime-idle callbacks before driver removal
Source: NVD (National Vulnerability Database)
Vulnerability 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.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞。攻击者利用该漏洞导致内核崩溃。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux f3ec4f87d607f40497afdb5ac03f11e2ea253d52 ~ 9a87375bb586515c0af63d5dcdcd58ec4acf20a6 -
LinuxLinux 2.6.36 -

II. Public POCs for CVE-2024-35809

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-35809

登录查看更多情报信息。

Same Patch Batch · Linux · 2024-05-17 · 135 CVEs total

CVE-2024-35834xsk: recycle buffer in case Rx queue was full
CVE-2023-52686powerpc/powernv: Add a null pointer check in opal_event_init()
CVE-2023-52684firmware: qcom: qseecom: fix memory leaks in error paths
CVE-2023-52683ACPI: LPIT: Avoid u32 multiplication overflow
CVE-2023-52682f2fs: fix to wait on block writeback for post_read case
CVE-2023-52681efivarfs: Free s_fs_info on unmount
CVE-2023-52680ALSA: scarlett2: Add missing error checks to *_ctl_get()
CVE-2023-52679of: Fix double free in of_parse_phandle_with_args_map
CVE-2023-52678drm/amdkfd: Confirm list is non-empty before utilizing list_first_entry in kfd_topology.c
CVE-2023-52677riscv: Check if the code to patch lies in the exit section
CVE-2023-52676bpf: Guard stack limits against 32bit overflow
CVE-2023-52675powerpc/imc-pmu: Add a null pointer check in update_events_in_group()
CVE-2023-52674ALSA: scarlett2: Add clamp() in scarlett2_mixer_ctl_put()
CVE-2024-35838wifi: mac80211: fix potential sta-link leak
CVE-2024-35837net: mvpp2: clear BM pool before initialization
CVE-2024-35836dpll: fix pin dump crash for rebound module
CVE-2024-35835net/mlx5e: fix a double-free in arfs_create_groups
CVE-2023-52664net: atlantic: eliminate double free in error handling logic
CVE-2024-35830media: tc358743: register v4l2 async device only after successful setup
CVE-2024-35831io_uring: Fix release of pinned pages when __io_uaddr_map fails

Showing top 20 of 135 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

V. Comments for CVE-2024-35809

No comments yet


Leave a comment