cpufreq: CPPC: Select the frequency-invariance callback per CPU
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 21e018235d99bc86249b034c06646df8757b2852, Kernel 309af21d334f970ad32175eefd1f33d154c1160d and Kernel 7.3.5.
In the Linux kernel, the following vulnerability has been resolved: cpufreq: CPPC: Select the frequency-invariance callback per CPU cppc_cpufreq_cpu_fie_init() initializes deferred work only for CPUs whose feedback counters use PCC. However, if any CPU in a shared policy uses PCC, it installs the PCC tick callback for the entire policy. With FIE enabled, a non-PCC CPU then queues an uninitialized irq_work and can call a NULL function pointer when that work runs. Choose the frequency-invariance callback separately for each CPU using the recorded work-initialization state. Processor removal can unpublish the CPC descriptor before callback registration, so querying its counter transport again can incorrectly select direct reads for a PCC CPU. Register the callbacks after all counter initialization has completed, so a failed initial read for an online CPU cannot leave a partially registered policy. PCC CPUs use their initialized deferred work, while non-PCC CPUs read their own counters directly from the tick.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =7.0, >=997c021abc6eb9cf7df39fa77fa5e666ad55e3a3 <21e018235d99bc86249b034c06646df8757b2852, >=997c021abc6eb9cf7df39fa77fa5e666ad55e3a3 <309af21d334f970ad32175eefd1f33d154c1160d | 21e018235d99bc86249b034c06646df8757b2852, 309af21d334f970ad32175eefd1f33d154c1160d |
| linux-kernel: Kernel | >=7.0.0 <7.3.5 | 7.3.5 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket