Devices left attached via incorrect rollback indexing
Published Sep 17, 2026 · Updated Sep 17, 2026
Incomplete UBI rollback in Linux Kernel allows local users to leave devices attached through failed module initialization. In drivers/mtd/ubi/build.c, ubi_init_attach() limits cleanup by the mtd= parameter index rather than the actual device slots, skipping attachments assigned higher explicit numbers. Triggering requires explicit device numbering and a later attachment failure; upstream does not specify a crash or privilege escalation.
Summary
What happened
Incomplete UBI rollback in Linux Kernel allows local users to leave devices attached through failed module initialization. In drivers/mtd/ubi/build.c, ubi_init_attach() limits cleanup by the mtd= parameter index rather than the actual device slots, skipping attachments assigned higher explicit numbers. Triggering requires explicit device numbering and a later attachment failure; upstream does not specify a crash or privilege escalation.
The record
- CVE
- CVE-2026-90216
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- Linux Foundation
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.11
- Affected versionversion=83ff59a066637a6c28844bbf43009459408240f4 <4417ab6ecad01cf2d01045ef8104c95a66b0e893
- Affected versionversion=83ff59a066637a6c28844bbf43009459408240f4 <552e565ed8846e7db143e4a6bdf3f5677453c686
- Affected versionversion=83ff59a066637a6c28844bbf43009459408240f4 <5b0a6b554e12a97f9771a9a9f4ea1f5457373c73
- Affected versionversion=83ff59a066637a6c28844bbf43009459408240f4 <6b92e66ec6dd8019e8efb2a568ef7c967c5a18c5
- Affected versionversion=83ff59a066637a6c28844bbf43009459408240f4 <83c978921688af40dcab6db74882d1ff9b0b765c
- Affected versionversion=83ff59a066637a6c28844bbf43009459408240f4 <87b3da4acb860605643ebee312178f13b20744cf
- Affected versionversion=83ff59a066637a6c28844bbf43009459408240f4 <9754f049d5f1945d4c691d1f52824eb8daf8f9be
- Affected versionversion=83ff59a066637a6c28844bbf43009459408240f4 <e3f7e58189bc222971ddc860f1716f37e51ba996
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started