CVE-2026-90216

ubi: Fix rollback for explicit UBI device numbers

N/A
Published: September 17, 2026 at 04:07 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.1183ff59a066637a6c28844bbf43009459408240f4
Vendor states this is fixed in 4417ab6ecad01cf2d01045ef8104c95a66b0e893 (fixed)
Vendor states this is fixed in 552e565ed8846e7db143e4a6bdf3f5677453c686 (fixed)
Vendor states this is fixed in 5b0a6b554e12a97f9771a9a9f4ea1f5457373c73 (fixed)
Vendor states this is fixed in 6b92e66ec6dd8019e8efb2a568ef7c967c5a18c5 (fixed)
Vendor states this is fixed in 83c978921688af40dcab6db74882d1ff9b0b765c (fixed)
Vendor states this is fixed in 87b3da4acb860605643ebee312178f13b20744cf (fixed)
Vendor states this is fixed in 9754f049d5f1945d4c691d1f52824eb8daf8f9be (fixed)
Vendor states this is fixed in e3f7e58189bc222971ddc860f1716f37e51ba996 (fixed)
Vendor states this is fixed in 3.11 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card