CVE-2024-43876: PCI: rcar: Demote WARN() to dev_warn_ratelimited() in rcar_pcie_wakeup()

Published Aug 21, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

PCI: rcar: Demote WARN() to devwarnratelimited() in rcarpciewakeup()

Avoid large backtrace, it is sufficient to warn the user that there has been a link problem. Either the link has failed and the system is in need of maintenance, or the link continues to work and user has been informed. The message from the warning can be looked up in the sources.

This makes an actual link issue less verbose.

First of all, this controller has a limitation in that the controller driver has to assist the hardware with transition to L1 link state by writing L1IATN to PMCTRL register, the L1 and L0 link state switching is not fully automatic on this controller.

In case of an ASMedia ASM1062 PCIe SATA controller which does not support ASPM, on entry to suspend or during platform pmtest, the SATA controller enters D3hot state and the link enters L1 state. If the SATA controller wakes up before rcarpciewakeup() was called and returns to D0, the link returns to L0 before the controller driver even started its transition to L1 link state. At this point, the SATA controller did send an PMENTERL1 DLLP to the PCIe controller and the PCIe controller received it, and the PCIe controller did set PMSR PMEL1RX bit.

Once rcarpciewakeup() is called, if the link is already back in L0 state and PMEL1RX bit is set, the controller driver has no way to determine if it should perform the link transition to L1 state, or treat the link as if it is in L0 state. Currently the driver attempts to perform the transition to L1 link state unconditionally, which in this specific case fails with a PMSR L1FAEG poll timeout, however the link still works as it is already back in L0 state.

Reduce this warning verbosity. In case the link is really broken, the rcarpcieconfigaccess() would fail, otherwise it will succeed and any system with this controller and ASM1062 can suspend without generating a backtrace.

Affected Software

5 affected componentsFixes available
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1
Linux Linux kernel>=5.18<6.1.103
Linux Linux kernel>=6.2<6.6.44
Linux Linux kernel>=6.7<6.10.3

Event History

Aug 21, 2024
CVE Published
via MITRE·12:06 AM
Data Sourced
via MITRE·12:06 AM
Description
Data Sourced
via NVD·01:15 AM
Description
Data Sourced
via NVD·01:15 AM
RemedySeverityAffected Software
Jan 9, 2025
Data Sourced
via Ubuntu·06:28 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-43876?

CVE-2024-43876 is considered a low to moderate severity vulnerability affecting the Linux kernel.

2

How do I fix CVE-2024-43876?

To fix CVE-2024-43876, update the Linux kernel to a version that includes the patch, such as 5.10.223-1 or 6.12.11-1.

3

What systems are affected by CVE-2024-43876?

CVE-2024-43876 affects specific versions of the Linux kernel, including 5.10.223-1, 5.10.226-1, 6.1.123-1, and others.

4

Is there a workaround for CVE-2024-43876?

There is no official workaround for CVE-2024-43876; the recommended action is to apply the necessary updates.

5

What does CVE-2024-43876 address in the Linux kernel?

CVE-2024-43876 addresses an issue related to PCI link problems by demoting excessive warnings in the rcar_pcie_wakeup function.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203