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-68416mtd: fix double free and WARN_ON in add_mtd_device() error paths

Description

In the Linux kernel, the following vulnerability has been resolved: mtd: fix double free and WARN_ON in add_mtd_device() error paths When device_register() or mtd_nvmem_add() fails inside add_mtd_device() for a partition, the error handling triggers mtd_release() via put_device() or device_unregister(). mtd_release() calls release_mtd_partition() which frees the mtd_info structure. However, callers such as mtd_add_partition() and add_mtd_partitions() also call free_partition() in their error paths, resulting in a double free. Additionally, release_mtd_partition() hits WARN_ON(!list_empty( &mtd->part.node)) because the partition node is still linked in the parent's partitions list when the release callback fires from the add_mtd_device() error path. Fix this by overriding dev->type and dev->release before put_device() in the error paths, so that device_release() invokes a no-op function instead of mtd_release(). For the mtd_nvmem_add() failure case, device_unregister() is replaced with device_del() to separate the device removal from the final kobject reference drop, allowing the override to take effect before put_device() is called. The callers' error paths (list_del + free_partition) remain the sole owners of mtd_info lifetime on add_mtd_device() failure, which is the expected contract. The normal partition teardown path is not affected: del_mtd_device() goes through kref_put() -> mtd_device_release() -> device_unregister() with dev->type still set to &mtd_devtype, so mtd_release() -> release_mtd_partition() continues to work correctly for the regular removal case.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 3 months 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.20% · top 91% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
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 93c08951d7070134b7415ca4abd0d25876aa653b – < b1f78dc4a6869e30ff64345a5d3e7da1b6da0061
    • affected 006764e33fe9cff72f8a68ce1dab570d93662c96 – < 1dfe90daee6080b088b65620ff690a56f59ddea2
    • affected 19bfa9ebebb5ec0695def57eb1d80de7e9cab369 – < ffe21a3545b439e7b11578a701c22a847c149561
    • affected 19bfa9ebebb5ec0695def57eb1d80de7e9cab369 – < e1e96aca1bdf391e2f49531c270ffc134e5b49a5
    • affected 19bfa9ebebb5ec0695def57eb1d80de7e9cab369 – < f98ae09c727dcf34f745c875661c64b642e4abfa
    • affected 19bfa9ebebb5ec0695def57eb1d80de7e9cab369 – < 820f983d641937a787e841ee4b93501f69f5683e
    • affected 19bfa9ebebb5ec0695def57eb1d80de7e9cab369 – < 9d4af746af8ce27eefc2338b2feaa1e01f28b6c3
  • Linux · Linux

    • affected 6.6
    • unaffected < 6.6
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .