6 matches found
Astra Linux – Vulnerabilities in Linux 5.10, Linux 5.15, Linux 6.1
In the Linux kernel, the following vulnerability has been resolved: cpufreq: intelpstate: A issue related to the object lifecycle was fixed in updateqosrequest. The cpufreqcpuput call in updateqosrequest occurs too early. This is because updateqosrequest subsequently calls freqqosupdaterequest,...
Linux Distros Unpatched Vulnerability : CVE-2025-40194
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - cpufreq: intelpstate: Fix object lifecycle issue in updateqosrequest The cpufreqcpuput call in updateqosrequest takes place too early because the latter...
CVE-2025-40194 cpufreq: intel_pstate: Fix object lifecycle issue in update_qos_request()
In the Linux kernel, the following vulnerability has been resolved: cpufreq: intelpstate: Fix object lifecycle issue in updateqosrequest The cpufreqcpuput call in updateqosrequest takes place too early because the latter subsequently calls freqqosupdaterequest that indirectly accesses the policy...
CVE-2025-40194
CVE-2025-40194 affects the Linux kernel cpufreq Intel_pstate driver. The vulnerability arises from an object lifecycle issue in update_qos_request() where cpufreq_cpu_put() is invoked too early, while freq_qos_update_request() may indirectly access the same policy object. The advisory notes that ...
CVE-2025-40194 cpufreq: intel_pstate: Fix object lifecycle issue in update_qos_request()
In the Linux kernel, the following vulnerability has been resolved: cpufreq: intelpstate: Fix object lifecycle issue in updateqosrequest The cpufreqcpuput call in updateqosrequest takes place too early because the latter subsequently calls freqqosupdaterequest that indirectly accesses the policy...
CVE-2025-40194
In the Linux kernel, the following vulnerability has been resolved: cpufreq: intelpstate: Fix object lifecycle issue in updateqosrequest The cpufreqcpuput call in updateqosrequest takes place too early because the latter subsequently calls freqqosupdaterequest that indirectly accesses the policy...