CVE-2026-90216: ubi: Fix rollback for explicit UBI device numbers
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 4417ab6ecad01cf2d01045ef8104c95a66b0e893, 552e565ed8846e7db143e4a6bdf3f5677453c686, 5b0a6b554e12a97f9771a9a9f4ea1f5457373c73.
Low priority for now. Upgrade to Linux Linux 4417ab6ecad01cf2d01045ef8104c95a66b0e893, 552e565ed8846e7db143e4a6bdf3f5677453c686, 5b0a6b554e12a97f9771a9a9f4ea1f5457373c73 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In 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.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.11affected
- 83ff59a066637a6c28844bbf43009459408240f4 and later · before 83c978921688af40dcab6db74882d1ff9b0b765caffected · git
- 83ff59a066637a6c28844bbf43009459408240f4 and later · before 6b92e66ec6dd8019e8efb2a568ef7c967c5a18c5affected · git
- 83ff59a066637a6c28844bbf43009459408240f4 and later · before 4417ab6ecad01cf2d01045ef8104c95a66b0e893affected · git
- 83ff59a066637a6c28844bbf43009459408240f4 and later · before 552e565ed8846e7db143e4a6bdf3f5677453c686affected · git
- 83ff59a066637a6c28844bbf43009459408240f4 and later · before 9754f049d5f1945d4c691d1f52824eb8daf8f9beaffected · git
- 83ff59a066637a6c28844bbf43009459408240f4 and later · before e3f7e58189bc222971ddc860f1716f37e51ba996affected · git
- 83ff59a066637a6c28844bbf43009459408240f4 and later · before 87b3da4acb860605643ebee312178f13b20744cfaffected · git
- 83ff59a066637a6c28844bbf43009459408240f4 and later · before 5b0a6b554e12a97f9771a9a9f4ea1f5457373c73affected · git
- before 3.11not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90214Sep 17, 2026 · ASoC: xilinx: formatter_pcm: fix stream_data leak on open error0Monitor
- ← EarlierCVE-2026-90215Sep 17, 2026 · mtd: ubi: Release device reference on busy detach0Monitor
- Later →CVE-2026-90217Sep 17, 2026 · bpf: Compare iterator types during state pruning31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 4417ab6ecad01cf2d01045ef8104c95a66b0e893 | Vendor (CNA) |
| Linux Linux | 552e565ed8846e7db143e4a6bdf3f5677453c686 | Vendor (CNA) |
| Linux Linux | 5b0a6b554e12a97f9771a9a9f4ea1f5457373c73 | Vendor (CNA) |
| Linux Linux | 6b92e66ec6dd8019e8efb2a568ef7c967c5a18c5 | Vendor (CNA) |
| Linux Linux | 83c978921688af40dcab6db74882d1ff9b0b765c | Vendor (CNA) |
| Linux Linux | 87b3da4acb860605643ebee312178f13b20744cf | Vendor (CNA) |
| Linux Linux | 9754f049d5f1945d4c691d1f52824eb8daf8f9be | Vendor (CNA) |
| Linux Linux | e3f7e58189bc222971ddc860f1716f37e51ba996 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/552e565ed8846e7db143e4a6bdf3f5677453c686
- git.kernel.org/stable/c/5b0a6b554e12a97f9771a9a9f4ea1f5457373c73
- git.kernel.org/stable/c/6b92e66ec6dd8019e8efb2a568ef7c967c5a18c5
- git.kernel.org/stable/c/83c978921688af40dcab6db74882d1ff9b0b765c
- git.kernel.org/stable/c/87b3da4acb860605643ebee312178f13b20744cf
- git.kernel.org/stable/c/9754f049d5f1945d4c691d1f52824eb8daf8f9be
- git.kernel.org/stable/c/e3f7e58189bc222971ddc860f1716f37e51ba996
Vendor advisories and official records. Exploit/PoC links are deliberately left out.