Vulnerability · 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_q
Published Nov 12, 2025 · catalog updated May 11, 2026 · Linux Linux
Open the advisory
Exploitation likelihood is not on this record for CVE-2025-40194. A missing EPSS score is not a low risk. Compare Linux Linux with the linked advisory before you change production.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- EPSS is missing. A missing score is not a low risk.
- Severity
- None0.0
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- Not in the current FIRST EPSS dataset
- Remediation
- Version ranges on file
- Affected products
- vendor Linux Linux da5c504c7aae96db68c4b38e2564a88e91842d89 <69e5d50fcf4093fb3f9f41c4f931f12c2ca8c467
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 rem
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor Linux Linux da5c504c7aae96db68c4b38e2564a88e91842d89 <69e5d50fcf4093fb3f9f41c4f931f12c2ca8c467da5c504c7aae96db68c4b38e2564a88e91842d89 <69e5d50fcf4093fb3f9f41c4f931f12c2ca8c467
How to fix CVE-2025-40194
Recommended remediation
Affected version ranges suggest a fixed boundary. Verify against the vendor advisory for your release.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
Exploitation likelihood is not on this record for CVE-2025-40194. A missing EPSS score is not a low risk. Compare Linux Linux with the linked advisory before you change production.
Which versions are affected?
Compare what you have installed with Linux Linux da5c504c7aae96db68c4b38e2564a88e91842d89 <69e5d50fcf4093fb3f9f41c4f931f12c2ca8c467 da5c504c7aae96db68c4b38e2564a88e91842d89 <69e5d50fcf4093fb3f9f41c4f931f12c2ca8c467. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS is absent from the current FIRST dataset. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Nov 12, 2025 · EUVD
Detected
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_q
May 11, 2026 · EUVD
Updated
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_q
Sources
- EUVDVulnerability recordEUVD-2025-150380
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() t
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Oct 23, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.