CVE-2026-90216 json
ubi: Fix rollback for explicit UBI device numbers
published 2026-09-17 52 d ago modified 2026-10-19 21 d ago also EUVD-2026-81809
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6, 7.3
- linux Debian 12 6.1.190-1
- linux Debian 13 6.12.111-1
- linux Debian 14 7.2.6-1
- linux-6.12 Debian 12 6.12.111-1~deb12u1
debian advisories DEBIAN-CVE-2026-90216
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-gke Ubuntu 22.04 LTS 5.15.0-1115.121
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1113.117
ubuntu advisories UBUNTU-CVE-2026-90216
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source openSUSE Tumbleweed 7.2.7-1.1
opensuse advisories openSUSE-SU-2026:11880-1
- kernel Azure Linux 3.0 6.6.157.1-1
azure linux advisories AZL-102449
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/83c978921688af40dcab6db74882d1ff9b0b765c commit
- git.kernel.org/stable/c/6b92e66ec6dd8019e8efb2a568ef7c967c5a18c5 commit
- git.kernel.org/stable/c/4417ab6ecad01cf2d01045ef8104c95a66b0e893 commit
- git.kernel.org/stable/c/552e565ed8846e7db143e4a6bdf3f5677453c686 commit
- git.kernel.org/stable/c/9754f049d5f1945d4c691d1f52824eb8daf8f9be commit
- git.kernel.org/stable/c/e3f7e58189bc222971ddc860f1716f37e51ba996 commit
- git.kernel.org/stable/c/87b3da4acb860605643ebee312178f13b20744cf commit
- git.kernel.org/stable/c/5b0a6b554e12a97f9771a9a9f4ea1f5457373c73 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-90216 updated cvss 5.5
kernel: ubi: Fix rollback for explicit UBI device numbers
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/83c978921688af40dcab6db74882d1ff9b0b765c
- git.kernel.org /stable/c/6b92e66ec6dd8019e8efb2a568ef7c967c5a18c5
- git.kernel.org /stable/c/4417ab6ecad01cf2d01045ef8104c95a66b0e893
- git.kernel.org /stable/c/552e565ed8846e7db143e4a6bdf3f5677453c686
- git.kernel.org /stable/c/9754f049d5f1945d4c691d1f52824eb8daf8f9be
- git.kernel.org /stable/c/e3f7e58189bc222971ddc860f1716f37e51ba996
- git.kernel.org /stable/c/87b3da4acb860605643ebee312178f13b20744cf
- git.kernel.org /stable/c/5b0a6b554e12a97f9771a9a9f4ea1f5457373c73
Sources
- CVE List CVE-2026-90216
- NVD CVE-2026-90216
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.