CVE-2026-68416mtd: fix double free and WARN_ON in add_mtd_device() error paths
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Aug 17, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 19bfa9ebebb5ec0695def57eb1d80de7e9cab369 before ffe21a3545b439e7b11578a701c22a847c149561; from 19bfa9ebebb5ec0695def57eb1d80de7e9cab369 before e1e96aca1bdf391e2f49531c270ffc134e5b49a5; from 19bfa9ebebb5ec0695def57eb1d80de7e9cab369 before f98ae09c727dcf34f745c875661c64b642e4abfa; from 19bfa9ebebb5ec0695def57eb1d80de7e9cab369 before 820f983d641937a787e841ee4b93501f69f5683e; 19bfa9ebebb5ec0695def57eb1d80de7e9cab369 builds before 9d4af746af8ce27eefc2338b2feaa1e01f28b6c3 | CNA record |
References
- https://git.kernel.org/stable/c/ffe21a3545b439e7b11578a701c22a847c149561
- https://git.kernel.org/stable/c/e1e96aca1bdf391e2f49531c270ffc134e5b49a5
- https://git.kernel.org/stable/c/f98ae09c727dcf34f745c875661c64b642e4abfa
- https://git.kernel.org/stable/c/820f983d641937a787e841ee4b93501f69f5683e
- https://git.kernel.org/stable/c/9d4af746af8ce27eefc2338b2feaa1e01f28b6c3
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.