CVE-2025-40194

UnknownEPSS 0.17%

Last modified

CVE-2025-40194 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.17% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.17%

6.8th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= da5c504c7aae96db68c4b38e2564a88e91842d89, < 15ac9579ebdaf22a37d7f60b3a8efc1029732ef9; >= da5c504c7aae96db68c4b38e2564a88e91842d89, < bc26564bcc659beb6d977cd6eb394041ec2f2851; >= da5c504c7aae96db68c4b38e2564a88e91842d89, < ad4e8f9bdbef11a19b7cb93e7f313bf59bdcc3b4; >= da5c504c7aae96db68c4b38e2564a88e91842d89, < 0a58d3e77b22b087a57831c87cafd360e144a5bd; >= da5c504c7aae96db68c4b38e2564a88e91842d89, < 69a18ff6c60e8e113420f15355fad862cb45d38e; >= da5c504c7aae96db68c4b38e2564a88e91842d89, < ba63d4e9857a72a89e71a4eff9f2cc8c283e94c3; >= da5c504c7aae96db68c4b38e2564a88e91842d89, < 57e4a6aadf12578b96a038373cffd54b3a58b092; >= da5c504c7aae96db68c4b38e2564a88e91842d89, < 69e5d50fcf4093fb3f9f41c4f931f12c2ca8c467
LinuxLinux5.4

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2025-40194?
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.
How severe is CVE-2025-40194?
Severity scoring for CVE-2025-40194 is pending analysis. The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2025-40194?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2025

Are you affected by CVE-2025-40194?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST