Linux Kernel up to 6.12.110/6.18.52/7.2.6/7.3-rc2 cpufreq cpufreq_policy_alloc race condition

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
8.7$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as very critical, has been found in Linux Kernel up to 6.12.110/6.18.52/7.2.6/7.3-rc2. This issue affects the function cpufreq_policy_alloc of the component cpufreq. The manipulation leads to race condition. This vulnerability is uniquely identified as CVE-2026-97904. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.12.110/6.18.52/7.2.6/7.3-rc2 and classified as very critical. This issue affects the function cpufreq_policy_alloc of the component cpufreq. The manipulation with an unknown input leads to a race condition vulnerability. Using CWE to declare the problem leads to CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: cpufreq: initialize policy rwsem before sysfs publication cpufreq_policy_alloc() initializes policy->rwsem after kobject_init_and_add() has created the policy sysfs directory and its default attributes. A sysfs access can therefore reach a policy callback before the semaphore has been initialized. Initialize policy->rwsem before publishing the policy kobject so sysfs callbacks always see an initialized semaphore.

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2026-97904 since 09/25/2026. The exploitation is known to be easy. The attack may be initiated remotely. Additional levels of successful authentication are required for exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/25/2026).

Upgrading to version 6.12.111, 6.18.53, 7.2.7 or 7.3-rc3 eliminates this vulnerability. Applying the patch dc11263cb05ed519758fd135fe08d611bad1f241/27c9b491bf7604e83b50c3bbfa18a30266ff345f/2cee937f779f69b195b37bbec1e888da9bfe9d58/3e5d1bf4bd687beb2cb4e32a07af695455925588 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.1
VulDB Meta Temp Score: 8.7

VulDB Base Score: 9.1
VulDB Temp Score: 8.7
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Race condition
CWE: CWE-362
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.12.111/6.18.53/7.2.7/7.3-rc3
Patch: dc11263cb05ed519758fd135fe08d611bad1f241/27c9b491bf7604e83b50c3bbfa18a30266ff345f/2cee937f779f69b195b37bbec1e888da9bfe9d58/3e5d1bf4bd687beb2cb4e32a07af695455925588

Timelineinfo

09/25/2026 Advisory disclosed
09/25/2026 +0 days CVE reserved
09/25/2026 +0 days VulDB entry created
09/25/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-97904 (🔒)
GCVE (CVE): GCVE-0-2026-97904
GCVE (VulDB): GCVE-100-410117

Entryinfo

Created: 09/25/2026 14:48
Changes: 09/25/2026 14:48 (59)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!