Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 83ff59a066637a6c28844bbf43009459408240f4 – < 83c978921688af40dcab6db74882d1ff9b0b765c
    • affected 83ff59a066637a6c28844bbf43009459408240f4 – < 6b92e66ec6dd8019e8efb2a568ef7c967c5a18c5
    • affected 83ff59a066637a6c28844bbf43009459408240f4 – < 4417ab6ecad01cf2d01045ef8104c95a66b0e893
    • affected 83ff59a066637a6c28844bbf43009459408240f4 – < 552e565ed8846e7db143e4a6bdf3f5677453c686
    • affected 83ff59a066637a6c28844bbf43009459408240f4 – < 9754f049d5f1945d4c691d1f52824eb8daf8f9be
    • affected 83ff59a066637a6c28844bbf43009459408240f4 – < e3f7e58189bc222971ddc860f1716f37e51ba996
    • affected 83ff59a066637a6c28844bbf43009459408240f4 – < 87b3da4acb860605643ebee312178f13b20744cf
    • affected 83ff59a066637a6c28844bbf43009459408240f4 – < 5b0a6b554e12a97f9771a9a9f4ea1f5457373c73
  • Linux · Linux

    • affected 3.11
    • unaffected < 3.11
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90216 badge
[![CVE-2026-90216](https://cveledger.app/badge/CVE-2026-90216.svg)](https://cveledger.app/cve/CVE-2026-90216)

Record last updated .