CVE-2024-26918
Last modified
CVE-2024-26918 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: PCI: Fix active state requirement in PME polling The commit noted in fixes added a bogus requirement that runtime PM managed devices need to be in the RPM_ACTIVE state for PME polling. In fact, only devices in low power states should be polled. However there's still a requirement that the device config space must be accessible, which has implications for both the current state of the polled device and the parent bridge, when present. EPSS estimates a 0.23% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: PCI: Fix active state requirement in PME polling The commit noted in fixes added a bogus requirement that runtime PM managed devices need to be in the RPM_ACTIVE state for PME polling. In fact, only devices in low power states should be polled. However there's still a requirement that the device config space must be accessible, which has implications for both the current state of the polled device and the parent bridge, when present. It's not sufficient to assume the bridge remains in D0 and cases have been observed where the bridge passes the D0 test, but the PM state indicates RPM_SUSPENDING and config space of the polled device becomes inaccessible during pci_pme_wakeup(). Therefore, since the bridge is already effectively required to be in the RPM_ACTIVE state, formalize this in the code and elevate the PM usage count to maintain the state while polling the subordinate device. This resolves a regression reported in the bugzilla below where a Thunderbolt/USB4 hierarchy fails to scan for an attached NVMe endpoint downstream of a bridge in a D3hot power state.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.6, < 6.6.18 | — |
| Linux | Linux Kernel | >= 6.7, < 6.7.6 | — |
| Linux | Linux Kernel | 6.8 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2024-26918?
How severe is CVE-2024-26918?
How do I fix CVE-2024-26918?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-26912In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26913In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-26914In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-26915In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26916In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26917In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26919In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-2692SiYuan version 3.0.3 allows executing arbitrary commands on …9
- CVE-2024-26920In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26921In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26922In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26923In the Linux kernel, the following vulnerability has been re…4.7
Are you affected by CVE-2024-26918?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
