cpufreq: intel_pstate: Fix object lifecycle issue in update_qos_request()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ da5c504c7aae96db68c4b38e2564a88e91842d89 · < ba63d4e9857a72a89e71a4eff9f2cc8c283e94c3| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's intel_pstate update_qos_request() releases a policy object reference before a subsequent QoS update can access that object. This could theoretically cause a crash during CPU device hot removal, which currently can occur only in virtualized environments. The input does not describe an attacker, authentication requirement, or user interaction.
Engineers running Linux kernels that support CPU device hot removal should check their kernel versions; affected versions are not specified.