GHSA-X3PG-C8FJ-93PV
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In 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.
{
"affected": [],
"aliases": [
"CVE-2026-93069"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:18:00Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nOPP: Fix cleanup ordering\n\nCommit 173e02d67494 (\"OPP: Initialize scope-based pointers inline\")\nadded initialization for all pointers. In some cases, the ordering was\nchanged so that *opp_table was initialized after *opp. This also changes\nthe order of the registered cleanup functions.\n\nWhen the cleanup happens, this can cause use-after-free errors when the\nlast reference is released and the release function _opp_kref_release\ntries to access the already freed opp-\u003eopp_table.\n\nInitialize *opp_table before *opp again to fix this and ensure the\ncorrect cleanup order.",
"id": "GHSA-x3pg-c8fj-93pv",
"modified": "2026-09-17T18:32:09Z",
"published": "2026-09-17T18:32:09Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93069"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ce46fede7792cedd247e34b48bc8a02eb90c7848"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f0c4b7ca24d2e2618a70826881d69b237e36bcc0"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.