CVE-2026-99787: cpufreq: CPPC: Select the frequency-invariance callback per CPU

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

cpufreq: CPPC: Select the frequency-invariance callback per CPU

cppccpufreqcpufieinit() 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 irqwork 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 Software

3 affected componentsFixes available
linux/kernel>=7.0.0<7.3.5
7.3.5
debian/linux*
debian/linux<=7.3.4-1
6.1.176-16.1.192-26.12.107-16.12.117-17.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  2. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 6.12.107-1Fixed in 6.12.117-1Fixed in 7.3.5-1

Event History

Nov 20, 2026
CVE Published
via MITRE·05:51 AM
Data Sourced
via MITRE·05:51 AM
Description
Data Sourced
via OSV·05:51 AM
DescriptionAffected Software
Data Sourced
via NVD·06:18 AM
Description

Frequently Asked Questions

1

Which systems are exposed to this issue?

Systems using the Linux kernel CPPC cpufreq driver with frequency invariance enabled are exposed when a shared CPU policy contains both CPUs whose feedback counters use PCC and CPUs that do not. The unsafe path occurs when the policy-wide PCC tick callback runs on a non-PCC CPU.

2

What must happen for the vulnerability to be triggered?

At least one CPU in a shared policy must use PCC, causing the PCC tick callback to be installed for the policy, and a non-PCC CPU in that policy must execute the callback. That CPU can queue irq_work that was never initialized, which can result in a NULL function-pointer call when the work runs.

3

Can processor removal affect the vulnerable behavior?

Yes. Processor removal can unpublish a CPU's CPC descriptor before callback registration; a later transport query can then misidentify a PCC CPU as using direct counter reads. The resolved behavior registers callbacks only after counter initialization is complete, avoiding partially registered policies when an initial read fails for an online CPU.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203