# CVE-2026-93069: OPP: Fix cleanup ordering

> A use-after-free vulnerability in the Linux kernel OPP subsystem allows local attackers to potentially execute code or escalate privileges due to incorrect cleanup ordering.

- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-93069, GHSA-x3pg-c8fj-93pv, UBUNTU-CVE-2026-93069

## What is CVE-2026-93069?

CVE-2026-93069 is an use after free vulnerability in Linux, published on 17 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:

OPP: Fix cleanup ordering

Commit 173e02d67494 ("OPP: Initialize scope-based pointers inline")
added initialization for all pointers. In some cases, the ordering was
changed so that *opp_table was initialized after *opp. This also changes
the order of the registered cleanup functions.

When the cleanup happens, this can cause use-after-free errors when the
last reference is released and the release function _opp_kref_release
tries to access the already freed opp->opp_table.

Initialize *opp_table before *opp again to fix this and ensure the
correct cleanup order.

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


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

Apply the vendor's patch.

## Is CVE-2026-93069 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93069 is an use after free vulnerability in Linux, published on 17 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-93069 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-93069/ (Markdown: https://insights.sbomify.com/CVE-2026-93069/index.md)
```

## Sources

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

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