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-2025-40194cpufreq: intel_pstate: Fix object lifecycle issue in update_qos_request()

Description

In the Linux kernel, the following vulnerability has been resolved: cpufreq: intel_pstate: Fix object lifecycle issue in update_qos_request() The cpufreq_cpu_put() call in update_qos_request() takes place too early because the latter subsequently calls freq_qos_update_request() that indirectly accesses the policy object in question through the QoS request object passed to it. Fortunately, update_qos_request() is called under intel_pstate_driver_lock, so this issue does not matter for changing the intel_pstate operation mode, but it theoretically can cause a crash to occur on CPU device hot removal (which currently can only happen in virt, but it is formally supported nevertheless). Address this issue by modifying update_qos_request() to drop the reference to the policy later.

Timeline

  1. ID reserved

    By Linux

  2. · 7 months later

    Published

  3. · 6 months 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (16 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected da5c504c7aae96db68c4b38e2564a88e91842d89 – < 15ac9579ebdaf22a37d7f60b3a8efc1029732ef9
    • affected da5c504c7aae96db68c4b38e2564a88e91842d89 – < bc26564bcc659beb6d977cd6eb394041ec2f2851
    • affected da5c504c7aae96db68c4b38e2564a88e91842d89 – < ad4e8f9bdbef11a19b7cb93e7f313bf59bdcc3b4
    • affected da5c504c7aae96db68c4b38e2564a88e91842d89 – < 0a58d3e77b22b087a57831c87cafd360e144a5bd
    • affected da5c504c7aae96db68c4b38e2564a88e91842d89 – < 69a18ff6c60e8e113420f15355fad862cb45d38e
    • affected da5c504c7aae96db68c4b38e2564a88e91842d89 – < ba63d4e9857a72a89e71a4eff9f2cc8c283e94c3
    • affected da5c504c7aae96db68c4b38e2564a88e91842d89 – < 57e4a6aadf12578b96a038373cffd54b3a58b092
    • affected da5c504c7aae96db68c4b38e2564a88e91842d89 – < 69e5d50fcf4093fb3f9f41c4f931f12c2ca8c467
  • Linux · Linux

    • affected 5.4
    • unaffected < 5.4
    • unaffected 5.4.301 – ≤ 5.4.*
    • unaffected 5.10.246 – ≤ 5.10.*
    • unaffected 5.15.195 – ≤ 5.15.*
    • unaffected 6.1.157 – ≤ 6.1.*
    • unaffected 6.6.113 – ≤ 6.6.*
    • unaffected 6.12.54 – ≤ 6.12.*
    • unaffected 6.17.4 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .