Answer in brief
CVE-2026-64372 records a Unknown severity vulnerability in cpufreq: pcc: fix use-after-free and double free in _OSC evaluation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-64372 records a Unknown severity vulnerability in cpufreq: pcc: fix use-after-free and double free in _OSC evaluation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=0f1d683fb35d6c6f49ef696c95757f3970682a0e <8e454e9d0bc03446d610ee49abec9dfd424f6541 || >=0f1d683fb35d6c6f49ef696c95757f3970682a0e <632666a63116d8061c62a988d1ca39dcd6d27c9b || >=0f1d683fb35d6c6f49ef696c95757f3970682a0e <5cdb25f144b101083d8bf3fd023ad87fbe6850d7 || >=0f1d683fb35d6c6f49ef696c95757f3970682a0e <982c9f92d57bda2b769851ff6d90d43dcf5f3734 || >=0f1d683fb35d6c6f49ef696c95757f3970682a0e <a36ca93a8ba57464e521d70a337d37f069064111 || >=0f1d683fb35d6c6f49ef696c95757f3970682a0e <6ba6f6783be2ffeb2cbcdc9321c4b9f708f796f7 || >=0f1d683fb35d6c6f49ef696c95757f3970682a0e <0e3c739a2f6fc1de5b19a8839ab80696b9cb2a29 || >=0f1d683fb35d6c6f49ef696c95757f3970682a0e <266d3dd8b757b48a576e90f018b51f7b7563cc32 | 8e454e9d0bc03446d610ee49abec9dfd424f6541, 632666a63116d8061c62a988d1ca39dcd6d27c9b, 5cdb25f144b101083d8bf3fd023ad87fbe6850d7, 982c9f92d57bda2b769851ff6d90d43dcf5f3734, a36ca93a8ba57464e521d70a337d37f069064111, 6ba6f6783be2ffeb2cbcdc9321c4b9f708f796f7, 0e3c739a2f6fc1de5b19a8839ab80696b9cb2a29, 266d3dd8b757b48a576e90f018b51f7b7563cc32 |
| Linux/Linuxgeneric | 2.6.34 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=0f1d683fb35d6c6f49ef696c95757f3970682a0e <8e454e9d0bc03446d610ee49abec9dfd424f6541 || >=0f1d683fb35d6c6f49ef696c95757f3970682a0e <632666a63116d8061c62a988d1ca39dcd6d27c9b || >=0f1d683fb35d6c6f49ef696c95757f3970682a0e <5cdb25f144b101083d8bf3fd023ad87fbe6850d7 || >=0f1d683fb35d6c6f49ef696c95757f3970682a0e <982c9f92d57bda2b769851ff6d90d43dcf5f3734 || >=0f1d683fb35d6c6f49ef696c95757f3970682a0e <a36ca93a8ba57464e521d70a337d37f069064111 || >=0f1d683fb35d6c6f49ef696c95757f3970682a0e <6ba6f6783be2ffeb2cbcdc9321c4b9f708f796f7 || >=0f1d683fb35d6c6f49ef696c95757f3970682a0e <0e3c739a2f6fc1de5b19a8839ab80696b9cb2a29 || >=0f1d683fb35d6c6f49ef696c95757f3970682a0e <266d3dd8b757b48a576e90f018b51f7b7563cc32 | 8e454e9d0bc03446d610ee49abec9dfd424f6541, 632666a63116d8061c62a988d1ca39dcd6d27c9b, 5cdb25f144b101083d8bf3fd023ad87fbe6850d7, 982c9f92d57bda2b769851ff6d90d43dcf5f3734, a36ca93a8ba57464e521d70a337d37f069064111, 6ba6f6783be2ffeb2cbcdc9321c4b9f708f796f7, 0e3c739a2f6fc1de5b19a8839ab80696b9cb2a29, 266d3dd8b757b48a576e90f018b51f7b7563cc32 |
| Linux/Linuxgeneric | 2.6.34 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.