CVE-2026-93069 (GCVE-0-2026-93069)
Vulnerability from cvelistv5 – Published: 2026-09-17 16:10 – Updated: 2026-09-17 16:10
VLAI
EPSS
VEX
Title
OPP: Fix cleanup ordering
Summary
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.
Severity
No CVSS data available.
Assigner
References
Impacted products
2 products
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
173e02d674946ff3ef8da7f44a9d5b820b9af21c , < f0c4b7ca24d2e2618a70826881d69b237e36bcc0
(git)
Affected: 173e02d674946ff3ef8da7f44a9d5b820b9af21c , < ce46fede7792cedd247e34b48bc8a02eb90c7848 (git) |
guessed | |
| Linux | Linux |
Affected:
6.19
Unaffected: 0 , < 6.19 (semver) Unaffected: 7.2.6 , ≤ 7.2.* (semver) Unaffected: 7.3-rc1 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/opp/core.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "f0c4b7ca24d2e2618a70826881d69b237e36bcc0",
"status": "affected",
"version": "173e02d674946ff3ef8da7f44a9d5b820b9af21c",
"versionType": "git"
},
{
"lessThan": "ce46fede7792cedd247e34b48bc8a02eb90c7848",
"status": "affected",
"version": "173e02d674946ff3ef8da7f44a9d5b820b9af21c",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/opp/core.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.19"
},
{
"lessThan": "6.19",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.6",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2.6",
"versionStartIncluding": "6.19",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3-rc1",
"versionStartIncluding": "6.19",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "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."
}
],
"providerMetadata": {
"dateUpdated": "2026-09-17T16:10:53.642Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/f0c4b7ca24d2e2618a70826881d69b237e36bcc0"
},
{
"url": "https://git.kernel.org/stable/c/ce46fede7792cedd247e34b48bc8a02eb90c7848"
}
],
"title": "OPP: Fix cleanup ordering",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-93069",
"datePublished": "2026-09-17T16:10:53.642Z",
"dateReserved": "2026-09-17T15:57:05.661Z",
"dateUpdated": "2026-09-17T16:10:53.642Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/opp/core.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "f0c4b7ca24d2e2618a70826881d69b237e36bcc0",
"status": "affected",
"version": "173e02d674946ff3ef8da7f44a9d5b820b9af21c",
"versionType": "git"
},
{
"lessThan": "ce46fede7792cedd247e34b48bc8a02eb90c7848",
"status": "affected",
"version": "173e02d674946ff3ef8da7f44a9d5b820b9af21c",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/opp/core.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.19"
},
{
"lessThan": "6.19",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.6",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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": "CVE-2026-93069",
"lastModified": "2026-09-17T17:18:00.757",
"metrics": {},
"published": "2026-09-17T17:18:00.757",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/ce46fede7792cedd247e34b48bc8a02eb90c7848"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/f0c4b7ca24d2e2618a70826881d69b237e36bcc0"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
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.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
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.
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.
Loading…
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.
Loading…