CVE-2024-26918
published 2024-04-17CVE-2024-26918: 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…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.23%
13.9th percentile
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.
Affected
10 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.7.7-1 (forky) | linux 6.7.7-1 (forky) |
| linux | linux | — | — |
| linux | linux | >= d3fcd7360338358aa0036bec6d2cf0e37a0ca624 < 63b1a3d9dd3b3f6d67f524e76270e66767090583 | 63b1a3d9dd3b3f6d67f524e76270e66767090583 |
| linux | linux | >= d3fcd7360338358aa0036bec6d2cf0e37a0ca624 < a4f12e5cbac2865c151d1e97e36eb24205afb23b | a4f12e5cbac2865c151d1e97e36eb24205afb23b |
| linux | linux | >= d3fcd7360338358aa0036bec6d2cf0e37a0ca624 < 41044d5360685e78a869d40a168491a70cdb7e73 | 41044d5360685e78a869d40a168491a70cdb7e73 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 6.7.7-1 | 6.7.7-1 |
| linux | linux_kernel | >= 0 < 6.7.7-1 | 6.7.7-1 |
| linux | linux_kernel | >= 6.6 < 6.6.18 | 6.6.18 |
| linux | linux_kernel | >= 6.7 < 6.7.6 | 6.7.6 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5LOW
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: PCI: Fix active state requirement in PME polling
vendor_redhat·2024-04-17·CVSS 5.5
CVE-2024-26918 [MEDIUM] kernel: PCI: Fix active state requirement in PME polling
kernel: PCI: Fix active state requirement in PME polling
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
Debian
CVE-2024-26918: linux - In the Linux kernel, the following vulnerability has been resolved: PCI: Fix ac...
vendor_debian·2024·CVSS 5.5
CVE-2024-26918 [MEDIUM] CVE-2024-26918: linux - In the Linux kernel, the following vulnerability has been resolved: PCI: Fix ac...
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 effectiv
GHSA
GHSA-qcrv-2gf7-9hrp: In the Linux kernel, the following vulnerability has been resolved:
PCI: Fix active state requirement in PME polling
The commit noted in fixes added
ghsa_unreviewed·2024-04-17
CVE-2024-26918 [MEDIUM] GHSA-qcrv-2gf7-9hrp: In the Linux kernel, the following vulnerability has been resolved:
PCI: Fix active state requirement in PME polling
The commit noted in fixes added
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 effe
OSV
CVE-2024-26918: 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
osv·2024-04-17·CVSS 5.5
CVE-2024-26918 [MEDIUM] CVE-2024-26918: 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
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 effectiv
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/41044d5360685e78a869d40a168491a70cdb7e73https://git.kernel.org/stable/c/63b1a3d9dd3b3f6d67f524e76270e66767090583https://git.kernel.org/stable/c/a4f12e5cbac2865c151d1e97e36eb24205afb23bhttps://git.kernel.org/stable/c/41044d5360685e78a869d40a168491a70cdb7e73https://git.kernel.org/stable/c/63b1a3d9dd3b3f6d67f524e76270e66767090583https://git.kernel.org/stable/c/a4f12e5cbac2865c151d1e97e36eb24205afb23b
2024-04-17
Published