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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 2
- StatusReceived → PublishedNVD modified 2026-10-19 08:59
- First seenunscoredNVD modified 2026-10-19 09:19
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 8
- https://git.kernel.org/stable/c/4417ab6ecad01cf2d01045ef8104c95a66b0e893
- https://git.kernel.org/stable/c/552e565ed8846e7db143e4a6bdf3f5677453c686
- https://git.kernel.org/stable/c/5b0a6b554e12a97f9771a9a9f4ea1f5457373c73
- https://git.kernel.org/stable/c/6b92e66ec6dd8019e8efb2a568ef7c967c5a18c5
- https://git.kernel.org/stable/c/83c978921688af40dcab6db74882d1ff9b0b765c
- https://git.kernel.org/stable/c/87b3da4acb860605643ebee312178f13b20744cf
- https://git.kernel.org/stable/c/9754f049d5f1945d4c691d1f52824eb8daf8f9be
- https://git.kernel.org/stable/c/e3f7e58189bc222971ddc860f1716f37e51ba996