CVE-2026-68416

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.

Gravité et risque d'exploitation

CVE-2026-68416 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.16 %, ce qui la place devant 4.4 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions <=6.12.*, 6.12.101, 0, <=7.1.*, <6.6, <=6.6.*, 6.18.42, <9d4af746af8ce27eefc2338b2feaa1e01f28b6c3, 7.1.6, 6.6, <820f983d641937a787e841ee4b93501f69f5683e, <e1e96aca1bdf391e2f49531c270ffc134e5b49a5, <ffe21a3545b439e7b11578a701c22a847c149561, <=6.18.*, <f98ae09c727dcf34f745c875661c64b642e4abfa, <=*, 6.6.148, 7.2, 19bfa9ebebb5ec0695def57eb1d80de7e9cab369) est présent sur votre parc.
• Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
• À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
• Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

• 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