ubi: Fix rollback for explicit UBI device numbers

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.

Timeline

1. Sep 17, 2026, 4:07 PM UTCCVE published
2. Oct 19, 2026, 8:59 AM UTCRecord last updated

Affected versions

• Linux Linux

  From 83ff59a066637a6c28844bbf43009459408240f4 · fixed in 83c978921688af40dcab6db74882d1ff9b0b765c; From 83ff59a066637a6c28844bbf43009459408240f4 · fixed in 6b92e66ec6dd8019e8efb2a568ef7c967c5a18c5; From 83ff59a066637a6c28844bbf43009459408240f4 · fixed in 4417ab6ecad01cf2d01045ef8104c95a66b0e893; From 83ff59a066637a6c28844bbf43009459408240f4 · fixed in 552e565ed8846e7db143e4a6bdf3f5677453c686; From 83ff59a066637a6c28844bbf43009459408240f4 · fixed in 9754f049d5f1945d4c691d1f52824eb8daf8f9be; From 83ff59a066637a6c28844bbf43009459408240f4 · fixed in e3f7e58189bc222971ddc860f1716f37e51ba996; From 83ff59a066637a6c28844bbf43009459408240f4 · fixed in 87b3da4acb860605643ebee312178f13b20744cf; From 83ff59a066637a6c28844bbf43009459408240f4 · fixed in 5b0a6b554e12a97f9771a9a9f4ea1f5457373c73

• Linux Linux

  3.11

• KernelLinux

  From 3.11.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6

References 8