Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-26918PCI: Fix active state requirement in PME polling

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.

Timeline

  1. ID reserved

    By Linux

  2. · 58 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-26918, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium6.2CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.2.

Affected products

  • Linux · Linux

    • affected d3fcd7360338358aa0036bec6d2cf0e37a0ca624 – < 63b1a3d9dd3b3f6d67f524e76270e66767090583
    • affected d3fcd7360338358aa0036bec6d2cf0e37a0ca624 – < a4f12e5cbac2865c151d1e97e36eb24205afb23b
    • affected d3fcd7360338358aa0036bec6d2cf0e37a0ca624 – < 41044d5360685e78a869d40a168491a70cdb7e73
  • Linux · Linux

    • affected 6.6
    • unaffected < 6.6
    • unaffected 6.6.18 – ≤ 6.6.*
    • unaffected 6.7.6 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-26918 badge
[![CVE-2024-26918](https://cveledger.app/badge/CVE-2024-26918.svg)](https://cveledger.app/cve/CVE-2024-26918)

Record last updated .