CVE-2025-40194

cpufreq: intel_pstate: Fix object lifecycle issue in update_qos_request()

N/A
Published: November 12, 2025 at 09:56 PM UTC
Updated: October 19, 2026 at 09:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.4da5c504c7aae96db68c4b38e2564a88e91842d89
Vendor states this is fixed in 0a58d3e77b22b087a57831c87cafd360e144a5bd (fixed)
Vendor states this is fixed in 15ac9579ebdaf22a37d7f60b3a8efc1029732ef9 (fixed)
Vendor states this is fixed in 57e4a6aadf12578b96a038373cffd54b3a58b092 (fixed)
Vendor states this is fixed in 69a18ff6c60e8e113420f15355fad862cb45d38e (fixed)
Vendor states this is fixed in 69e5d50fcf4093fb3f9f41c4f931f12c2ca8c467 (fixed)
Vendor states this is fixed in ad4e8f9bdbef11a19b7cb93e7f313bf59bdcc3b4 (fixed)
Vendor states this is fixed in ba63d4e9857a72a89e71a4eff9f2cc8c283e94c3 (fixed)
Vendor states this is fixed in bc26564bcc659beb6d977cd6eb394041ec2f2851 (fixed)
Vendor states this is fixed in 5.10.246 (unaffected)
Vendor states this is fixed in 5.15.195 (unaffected)
Vendor states this is fixed in 5.4 (unaffected)
Vendor states this is fixed in 5.4.301 (unaffected)
Vendor states this is fixed in 6.1.157 (unaffected)
Vendor states this is fixed in 6.12.54 (unaffected)
Vendor states this is fixed in 6.17.4 (unaffected)
Vendor states this is fixed in 6.18 (unaffected)
Vendor states this is fixed in 6.6.113 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card