VulnerabilityPublished 17 Sep 2026Updated 19 Oct 2026

CVE-2026-93069: Linux kernel · OPP: Fix cleanup ordering

Affects Linux kernelSource CVE Database V5

Not known to be exploited : upgrade to f0c4b7ca24d2e2618a70826881d69b237e36bcc0 or ce46fede7792cedd247e34b48bc8a02eb90c7848 when convenient.

Data as of 26 Oct 2026, 12:55 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in f0c4b7ca24d2e2618a70826881d69b237e36bcc0, ce46fede7792cedd247e34b48bc8a02eb90c7848

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to f0c4b7ca24d2e2618a70826881d69b237e36bcc0 or ce46fede7792cedd247e34b48bc8a02eb90c7848.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 173e02d674946ff3ef8da7f44a9d5b820b9af21c, < f0c4b7ca24d2e2618a70826881d69b237e36bcc0	Fixed in f0c4b7ca24d2e2618a70826881d69b237e36bcc0
LinuxLinux	Affected ≥ 173e02d674946ff3ef8da7f44a9d5b820b9af21c, < ce46fede7792cedd247e34b48bc8a02eb90c7848	Fixed in ce46fede7792cedd247e34b48bc8a02eb90c7848
LinuxLinux	Affected =6.19	Fixed in–

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.

References

Community reviews

Loading reviews…