Linux Kernel up to 7.1.3 pcc pcc_cpufreq_do_osc use after free

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.4$0-$5k3.99

Summaryinfo

A vulnerability has been found in Linux Kernel up to 7.1.3 and classified as very critical. The affected element is the function pcc_cpufreq_do_osc of the component pcc. Performing a manipulation results in use after free. This vulnerability is cataloged as CVE-2026-64372. The attack must be initiated from a local position. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as very critical, was found in Linux Kernel up to 7.1.3. This affects the function pcc_cpufreq_do_osc of the component pcc. The manipulation with an unknown input leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: cpufreq: pcc: fix use-after-free and double free in _OSC evaluation pcc_cpufreq_do_osc() calls acpi_evaluate_object() twice for the two-phase _OSC negotiation. Between the two calls it freed output.pointer but left output.length unchanged. Since acpi_evaluate_object() treats a non-zero length with a non-NULL pointer as an existing buffer to write into, the second call wrote into freed memory (use-after-free). The subsequent kfree(output.pointer) at out_free then freed the same pointer a second time (double free). Reset output.pointer to NULL and output.length to ACPI_ALLOCATE_BUFFER after freeing the first result, so ACPICA allocates a fresh buffer for each phase independently.

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-64372 since 07/19/2026. The exploitability is told to be easy. An attack has to be approached locally. 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 07/25/2026).

Upgrading to version 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96, 6.18.39, 7.1.4 or 7.2-rc1 eliminates this vulnerability. Applying the patch 8e454e9d0bc03446d610ee49abec9dfd424f6541/632666a63116d8061c62a988d1ca39dcd6d27c9b/5cdb25f144b101083d8bf3fd023ad87fbe6850d7/982c9f92d57bda2b769851ff6d90d43dcf5f3734/a36ca93a8ba57464e521d70a337d37f069064111/6ba6f6783be2ffeb2cbcdc9321c4b9f708f796f7/0e3c739a2f6fc1de5b19a8839ab80696b9cb2a29/266d3dd8b757b48a576e90f018b51f7b7563cc32 is able to eliminate this problem.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.8
VulDB Meta Temp Score: 8.4

VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

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 5.10.261/5.15.212/6.1.178/6.6.145/6.12.96/6.18.39/7.1.4/7.2-rc1
Patch: 8e454e9d0bc03446d610ee49abec9dfd424f6541/632666a63116d8061c62a988d1ca39dcd6d27c9b/5cdb25f144b101083d8bf3fd023ad87fbe6850d7/982c9f92d57bda2b769851ff6d90d43dcf5f3734/a36ca93a8ba57464e521d70a337d37f069064111/6ba6f6783be2ffeb2cbcdc9321c4b9f708f796f7/0e3c739a2f6fc1de5b19a8839ab80696b9cb2a29/266d3dd8b757b48a576e90f018b51f7b7563cc32

Timelineinfo

07/19/2026 CVE reserved
07/25/2026 +6 days Advisory disclosed
07/25/2026 +0 days VulDB entry created
07/25/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-64372 (🔒)
GCVE (CVE): GCVE-0-2026-64372
GCVE (VulDB): GCVE-100-383169

Entryinfo

Created: 07/25/2026 17:38
Changes: 07/25/2026 17:38 (59)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!