GHSA-98X6-774G-8659
Vulnerability from github – Published: 2026-09-17 18:31 – Updated: 2026-09-17 18:31In the Linux kernel, the following vulnerability has been resolved:
ubi: Fix rollback for explicit UBI device numbers
ubi_init_attach() rolls back module initialization failures by scanning ubi_devices[0..i-1], where i is the mtd= parameter index. That assumes the parameter index matches the UBI device number.
That assumption is not true when mtd= specifies an explicit ubi_num. A successfully attached device can be stored at a higher ubi_devices[] slot, and a later failure can miss it during rollback.
Scan the full ubi_devices[] array and detach by the actual array index, matching the way UBI devices are stored.
{
"affected": [],
"aliases": [
"CVE-2026-90216"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:16Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nubi: Fix rollback for explicit UBI device numbers\n\nubi_init_attach() rolls back module initialization failures by scanning\nubi_devices[0..i-1], where i is the mtd= parameter index. That assumes\nthe parameter index matches the UBI device number.\n\nThat assumption is not true when mtd= specifies an explicit ubi_num. A\nsuccessfully attached device can be stored at a higher ubi_devices[]\nslot, and a later failure can miss it during rollback.\n\nScan the full ubi_devices[] array and detach by the actual array index,\nmatching the way UBI devices are stored.",
"id": "GHSA-98x6-774g-8659",
"modified": "2026-09-17T18:31:56Z",
"published": "2026-09-17T18:31:55Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90216"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4417ab6ecad01cf2d01045ef8104c95a66b0e893"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/552e565ed8846e7db143e4a6bdf3f5677453c686"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5b0a6b554e12a97f9771a9a9f4ea1f5457373c73"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/6b92e66ec6dd8019e8efb2a568ef7c967c5a18c5"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/83c978921688af40dcab6db74882d1ff9b0b765c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/87b3da4acb860605643ebee312178f13b20744cf"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9754f049d5f1945d4c691d1f52824eb8daf8f9be"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e3f7e58189bc222971ddc860f1716f37e51ba996"
}
],
"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.