- Vulnerability/
- CVE-2024-53152
CVE-2024-53152: PCI: tegra194: Move controller cleanups to pex_ep_event_pex_rst_deassert()
First published: Tue Dec 24 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: PCI: tegra194: Move controller cleanups to pex_ep_event_pex_rst_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 pex_ep_event_pex_rst_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 tegra194 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(), etc...). So these cleanup functions can cause 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. Thus, fix this crash by moving the controller cleanups to the start of the pex_ep_event_pex_rst_deassert() function. This function 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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | ||
| debian/linux | 5.10.223-1 5.10.226-1 6.1.123-1 6.1.128-1 6.12.12-1 6.12.15-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/40e2125381dc11379112485e3eefdd25c6df5375
- https://git.kernel.org/stable/c/70212c2300971506e986d95000d2745529cac9d7
- https://git.kernel.org/stable/c/72034050ccf4202cd6558b0afd2474f756ea3b9b
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-53152
- https://nvd.nist.gov/vuln/detail/CVE-2024-53152
- https://launchpad.net/bugs/cve/CVE-2024-53152
- https://security-tracker.debian.org/tracker/CVE-2024-53152
- https://ubuntu.com/security/CVE-2024-53152
- https://git.kernel.org/linus/40e2125381dc11379112485e3eefdd25c6df5375
Frequently Asked Questions
What is the severity of CVE-2024-53152?
CVE-2024-53152 has been classified with a severity level that is contingent on the specific system configurations and usage.
How do I fix CVE-2024-53152?
To fix CVE-2024-53152, users should apply the latest patches and updates available for the Linux Kernel.
What components are affected by CVE-2024-53152?
CVE-2024-53152 affects the Linux Kernel, specifically related to PCI controller cleanups in tegra194.
Is CVE-2024-53152 actively being exploited?
As of now, there are no public reports indicating that CVE-2024-53152 is being actively exploited.
What versions of the Linux Kernel are impacted by CVE-2024-53152?
CVE-2024-53152 impacts various versions of the Linux Kernel, and all users are recommended to check their versions for vulnerabilities.
- agent/severity
- agent/title
- agent/type
- agent/first-publish-date
- collector/nvd-api
- source/NVD
- agent/author
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/usn-cve
- source/Ubuntu
- agent/source
- agent/references
- agent/softwarecombine
- agent/tags
- agent/description
- collector/security-tracker-debian
- source/Debian
- agent/event
- vendor/linux
- canonical/linux kernel
- package-manager/debian