# CVE-2026-89572: cpufreq: apple-soc: Fix OPP table cleanup

> A memory management error in the Apple SoC cpufreq driver can lead to system crashes or instability due to improper OPP table cleanup.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-100797, BELL-CVE-2026-89572, DEBIAN-CVE-2026-89572, GHSA-pmg8-6cwh-c6vh, UBUNTU-CVE-2026-89572

## What is CVE-2026-89572?

CVE-2026-89572 is a memory corruption vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

cpufreq: apple-soc: Fix OPP table cleanup

apple_soc_cpufreq_init() adds OPP tables from firmware, but
some failure paths do not remove them. The driver also uses
dev_pm_opp_remove_all_dynamic(), which is not the right cleanup
helper for OPP tables loaded from firmware.

Use the cpumask OPP helper after the policy CPU mask has been
populated. Pair it with the matching cpumask remove helper on
failure paths and in apple_soc_cpufreq_exit(). This also removes
the separate dev_pm_opp_set_sharing_cpus() call, as the cpumask
helper loads the DT OPP tables for all CPUs in the policy.

## Which versions are affected by CVE-2026-89572?


## How do I fix CVE-2026-89572?

Apply the vendor's patch.

## Is CVE-2026-89572 being exploited?

There is no known exploitation of CVE-2026-89572 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-89572 and fix it if it is affected.

What it is: CVE-2026-89572 is a memory corruption vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89572 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-89572/ (Markdown: https://insights.sbomify.com/CVE-2026-89572/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-89572
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-89572
- OSV: https://osv.dev/vulnerability/CVE-2026-89572

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-89572/
Summaries are generated and may contain mistakes; the official description above is the record.