Excessive kernel logging via stale PCIe link state
Published Aug 21, 2024 · Updated May 11, 2026
Improper PCIe link-state handling in Linux allows attackers to trigger a kernel warning backtrace during system suspend. In rcar_pcie_wakeup(), the R-Car host driver requests L1 after an ASMedia ASM1062 has already returned the link to L0, causing an L1FAEG poll timeout and WARN() backtrace. Reachability requires the R-Car PCIe controller, the non-ASPM ASM1062 device, and a suspend timing sequence; the link can remain operational despite the warning.
Summary
What happened
Improper PCIe link-state handling in Linux allows attackers to trigger a kernel warning backtrace during system suspend. In rcar_pcie_wakeup(), the R-Car host driver requests L1 after an ASMedia ASM1062 has already returned the link to L0, causing an L1FAEG poll timeout and WARN() backtrace. Reachability requires the R-Car PCIe controller, the non-ASPM ASM1062 device, and a suspend timing sequence; the link can remain operational despite the warning.
The record
- CVE
- CVE-2024-43876
- Published
- Aug 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 21, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.18
- Affected versionversion=84b576146294c2be702cfcd174eaa74167e276f9 <2ae4769332dfdb97f4b6f5dc9ac8f46d02aaa3df
- Affected versionversion=84b576146294c2be702cfcd174eaa74167e276f9 <3ff3bdde950f1840df4030726cef156758a244d7
- Affected versionversion=84b576146294c2be702cfcd174eaa74167e276f9 <526a877c6273d4cd0d0aede84c1d620479764b1c
- Affected versionversion=84b576146294c2be702cfcd174eaa74167e276f9 <c93637e6a4c4e1d0e85ef7efac78d066bbb24d96
- Affected versionversion=9e14fb714ebf55443dd3449de9ea2ffcf13e562a <59c78e8fddc1fe68f14011450a09b3418127d2ad
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo