CVE-2024-53153: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: PCI: qcom-ep: Move controller cleanups to qcom_pcie_perst_deassert() Currently, the endpoint cleanup function dw_pcie_ep_cleanup() and EPF deinit notify function pci_epc_deinit_notify() are called during the execution of qcom_pcie_perst_assert() i.e., when the host has asserted PERST#. But quickly after this step, refclk will also be disabled by the host. All of the Qcom endpoint SoCs supported as of now depend on the refclk from the host for keeping the controller operational. Due to this limitation, any access to the hardware registers in the absence of refclk will result in a whole endpoint crash. Unfortunately, most of the controller cleanups require accessing the hardware registers (like eDMA cleanup performed in dw_pcie_ep_cleanup(), powering down MHI EPF etc...). So these cleanup functions are currently causing the crash in the endpoint SoC once host asserts PERST#. One way to address this issue is by generating the refclk in the endpoint itself and not depending on the host. But that is not always possible as some of the endpoint designs do require the endpoint to consume refclk from the host (as I was told by the Qcom engineers). Thus, fix this crash by moving the controller cleanups to the start of the qcom_pcie_perst_deassert() function. qcom_pcie_perst_deassert() is called whenever the host has deasserted PERST# and it is guaranteed that the refclk would be active at this point. So at the start of this function (after enabling resources), the controller cleanup can be performed. Once finished, rest of the code execution for PERST# deassert can continue as usual.
AI Analysis
Technical Summary
CVE-2024-53153 is a vulnerability identified in the Linux kernel specifically related to the Qualcomm PCIe endpoint controller (qcom-ep). The issue arises from the timing of controller cleanup functions during the assertion of the PCIe reset signal (PERST#) by the host. In the vulnerable state, cleanup functions such as dw_pcie_ep_cleanup() and pci_epc_deinit_notify() are executed when the host asserts PERST#, a time when the reference clock (refclk) provided by the host is disabled shortly thereafter. Since Qualcomm endpoint SoCs depend on this refclk to keep the PCIe controller operational, accessing hardware registers without an active refclk causes the entire endpoint to crash. The root cause is that cleanup operations require register access, which is invalid without the refclk, leading to a system crash. The vulnerability cannot be fully mitigated by generating the refclk internally on the endpoint side due to design constraints in some Qualcomm SoCs. The implemented fix involves moving the cleanup routines to the start of the qcom_pcie_perst_deassert() function, which is invoked when the host deasserts PERST# and the refclk is guaranteed to be active. This change ensures that cleanup occurs only when hardware registers are accessible, preventing crashes. This vulnerability affects Linux kernel versions containing the affected Qualcomm PCIe endpoint driver code and impacts systems using Qualcomm endpoint SoCs relying on host-supplied refclk for PCIe operations.
Potential Impact
For European organizations, the impact of CVE-2024-53153 primarily concerns systems running Linux kernels with Qualcomm PCIe endpoint SoCs that depend on host-supplied refclk. Affected devices could include embedded systems, networking equipment, IoT devices, and industrial control systems that utilize Qualcomm SoCs with this PCIe controller design. The vulnerability can cause endpoint crashes during PCIe reset sequences, potentially leading to system instability, device malfunctions, or denial of service conditions. In critical infrastructure or industrial environments, such crashes could disrupt operations or degrade system reliability. Although no known exploits are currently reported in the wild, the vulnerability could be leveraged by attackers with local access or through crafted PCIe interactions to induce crashes, impacting availability. The confidentiality and integrity impact is limited since the vulnerability causes crashes rather than unauthorized data access or code execution. However, availability degradation in critical systems could have cascading effects on business continuity and operational safety in sectors such as telecommunications, manufacturing, and transportation within Europe.
Mitigation Recommendations
To mitigate CVE-2024-53153, European organizations should: 1) Ensure Linux kernel versions are updated to include the patch that moves controller cleanup to qcom_pcie_perst_deassert(), thereby avoiding register access without refclk. 2) Audit and identify devices using Qualcomm endpoint SoCs with host-supplied refclk PCIe controllers, prioritizing firmware and kernel updates on these systems. 3) For embedded and industrial devices where kernel updates may be delayed, consider implementing hardware or firmware workarounds that ensure refclk stability during PCIe reset sequences or isolate vulnerable endpoints to minimize impact. 4) Monitor system logs and PCIe reset events for signs of endpoint crashes or instability that could indicate unpatched systems. 5) Engage with device vendors and Qualcomm for guidance on secure firmware versions and best practices for endpoint PCIe controller management. 6) Incorporate this vulnerability into risk assessments for critical systems using affected hardware to plan for timely patch deployment and incident response readiness.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Sweden, Finland
CVE-2024-53153: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: PCI: qcom-ep: Move controller cleanups to qcom_pcie_perst_deassert() Currently, the endpoint cleanup function dw_pcie_ep_cleanup() and EPF deinit notify function pci_epc_deinit_notify() are called during the execution of qcom_pcie_perst_assert() i.e., when the host has asserted PERST#. But quickly after this step, refclk will also be disabled by the host. All of the Qcom endpoint SoCs supported as of now depend on the refclk from the host for keeping the controller operational. Due to this limitation, any access to the hardware registers in the absence of refclk will result in a whole endpoint crash. Unfortunately, most of the controller cleanups require accessing the hardware registers (like eDMA cleanup performed in dw_pcie_ep_cleanup(), powering down MHI EPF etc...). So these cleanup functions are currently causing the crash in the endpoint SoC once host asserts PERST#. One way to address this issue is by generating the refclk in the endpoint itself and not depending on the host. But that is not always possible as some of the endpoint designs do require the endpoint to consume refclk from the host (as I was told by the Qcom engineers). Thus, fix this crash by moving the controller cleanups to the start of the qcom_pcie_perst_deassert() function. qcom_pcie_perst_deassert() is called whenever the host has deasserted PERST# and it is guaranteed that the refclk would be active at this point. So at the start of this function (after enabling resources), the controller cleanup can be performed. Once finished, rest of the code execution for PERST# deassert can continue as usual.
AI-Powered Analysis
Technical Analysis
CVE-2024-53153 is a vulnerability identified in the Linux kernel specifically related to the Qualcomm PCIe endpoint controller (qcom-ep). The issue arises from the timing of controller cleanup functions during the assertion of the PCIe reset signal (PERST#) by the host. In the vulnerable state, cleanup functions such as dw_pcie_ep_cleanup() and pci_epc_deinit_notify() are executed when the host asserts PERST#, a time when the reference clock (refclk) provided by the host is disabled shortly thereafter. Since Qualcomm endpoint SoCs depend on this refclk to keep the PCIe controller operational, accessing hardware registers without an active refclk causes the entire endpoint to crash. The root cause is that cleanup operations require register access, which is invalid without the refclk, leading to a system crash. The vulnerability cannot be fully mitigated by generating the refclk internally on the endpoint side due to design constraints in some Qualcomm SoCs. The implemented fix involves moving the cleanup routines to the start of the qcom_pcie_perst_deassert() function, which is invoked when the host deasserts PERST# and the refclk is guaranteed to be active. This change ensures that cleanup occurs only when hardware registers are accessible, preventing crashes. This vulnerability affects Linux kernel versions containing the affected Qualcomm PCIe endpoint driver code and impacts systems using Qualcomm endpoint SoCs relying on host-supplied refclk for PCIe operations.
Potential Impact
For European organizations, the impact of CVE-2024-53153 primarily concerns systems running Linux kernels with Qualcomm PCIe endpoint SoCs that depend on host-supplied refclk. Affected devices could include embedded systems, networking equipment, IoT devices, and industrial control systems that utilize Qualcomm SoCs with this PCIe controller design. The vulnerability can cause endpoint crashes during PCIe reset sequences, potentially leading to system instability, device malfunctions, or denial of service conditions. In critical infrastructure or industrial environments, such crashes could disrupt operations or degrade system reliability. Although no known exploits are currently reported in the wild, the vulnerability could be leveraged by attackers with local access or through crafted PCIe interactions to induce crashes, impacting availability. The confidentiality and integrity impact is limited since the vulnerability causes crashes rather than unauthorized data access or code execution. However, availability degradation in critical systems could have cascading effects on business continuity and operational safety in sectors such as telecommunications, manufacturing, and transportation within Europe.
Mitigation Recommendations
To mitigate CVE-2024-53153, European organizations should: 1) Ensure Linux kernel versions are updated to include the patch that moves controller cleanup to qcom_pcie_perst_deassert(), thereby avoiding register access without refclk. 2) Audit and identify devices using Qualcomm endpoint SoCs with host-supplied refclk PCIe controllers, prioritizing firmware and kernel updates on these systems. 3) For embedded and industrial devices where kernel updates may be delayed, consider implementing hardware or firmware workarounds that ensure refclk stability during PCIe reset sequences or isolate vulnerable endpoints to minimize impact. 4) Monitor system logs and PCIe reset events for signs of endpoint crashes or instability that could indicate unpatched systems. 5) Engage with device vendors and Qualcomm for guidance on secure firmware versions and best practices for endpoint PCIe controller management. 6) Incorporate this vulnerability into risk assessments for critical systems using affected hardware to plan for timely patch deployment and incident response readiness.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-11-19T17:17:25.000Z
- Cisa Enriched
- false
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9823c4522896dcbded6c
Added to database: 5/21/2025, 9:08:51 AM
Last enriched: 6/28/2025, 10:11:07 AM
Last updated: 7/28/2025, 9:08:15 PM
Views: 12
Related Threats
CVE-2025-8950: SQL Injection in Campcodes Online Recruitment Management System
MediumCVE-2025-27388: CWE-20 Improper Input Validation in OPPO OPPO HEALTH APP
HighCVE-2025-8949: Stack-based Buffer Overflow in D-Link DIR-825
HighCVE-2025-8948: SQL Injection in projectworlds Visitor Management System
MediumCVE-2025-8947: SQL Injection in projectworlds Visitor Management System
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.