CVE-2026-68416
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.
Leer descripción completaMostrar menos
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
NVD no ha asignado puntuación CVSS a esta CVE (habitual desde el cambio de política de abril de 2026).
Probabilidad de explotación (EPSS)
- Probabilidad de explotación en los próximos 30 días: 0.21%
- Percentil entre todas las CVEs puntuadas: 10
- Fecha de la puntuación: 6/10/2026
EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).
Tecnologías afectadas (1)
⚠ Inferidas por IA a partir de la descripción — NVD aún no ha analizado esta CVE; no son CPE verificados.
Referencias
- https://git.kernel.org/stable/c/820f983d641937a787e841ee4b93501f69f5683e
- https://git.kernel.org/stable/c/9d4af746af8ce27eefc2338b2feaa1e01f28b6c3
- https://git.kernel.org/stable/c/e1e96aca1bdf391e2f49531c270ffc134e5b49a5
- https://git.kernel.org/stable/c/f98ae09c727dcf34f745c875661c64b642e4abfa
- https://git.kernel.org/stable/c/ffe21a3545b439e7b11578a701c22a847c149561
JSON original (NVD)
Mostrar
{
"id": "CVE-2026-68416",
"cveTags": [],
"metrics": {},
"affected": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"affectedData": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "19bfa9ebebb5ec0695def57eb1d80de7e9cab369",
"lessThan": "ffe21a3545b439e7b11578a701c22a847c149561",
"versionType": "git"
},
{
"status": "affected",
"version": "19bfa9ebebb5ec0695def57eb1d80de7e9cab369",
"lessThan": "e1e96aca1bdf391e2f49531c270ffc134e5b49a5",
"versionType": "git"
},
{
"status": "affected",
"version": "19bfa9ebebb5ec0695def57eb1d80de7e9cab369",
"lessThan": "f98ae09c727dcf34f745c875661c64b642e4abfa",
"versionType": "git"
},
{
"status": "affected",
"version": "19bfa9ebebb5ec0695def57eb1d80de7e9cab369",
"lessThan": "820f983d641937a787e841ee4b93501f69f5683e",
"versionType": "git"
},
{
"status": "affected",
"version": "19bfa9ebebb5ec0695def57eb1d80de7e9cab369",
"lessThan": "9d4af746af8ce27eefc2338b2feaa1e01f28b6c3",
"versionType": "git"
}
],
"programFiles": [
"drivers/mtd/mtdcore.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "6.6"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "6.6",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "6.6.148",
"versionType": "semver",
"lessThanOrEqual": "6.6.*"
},
{
"status": "unaffected",
"version": "6.12.101",
"versionType": "semver",
"lessThanOrEqual": "6.12.*"
},
{
"status": "unaffected",
"version": "6.18.42",
"versionType": "semver",
"lessThanOrEqual": "6.18.*"
},
{
"status": "unaffected",
"version": "7.1.6",
"versionType": "semver",
"lessThanOrEqual": "7.1.*"
},
{
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"drivers/mtd/mtdcore.c"
],
"defaultStatus": "affected"
}
]
}
],
"published": "2026-08-10T13:20:35.383",
"references": [
{
"url": "https://git.kernel.org/stable/c/820f983d641937a787e841ee4b93501f69f5683e",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/9d4af746af8ce27eefc2338b2feaa1e01f28b6c3",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/e1e96aca1bdf391e2f49531c270ffc134e5b49a5",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/f98ae09c727dcf34f745c875661c64b642e4abfa",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/ffe21a3545b439e7b11578a701c22a847c149561",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"vulnStatus": "Received",
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmtd: fix double free and WARN_ON in add_mtd_device() error paths\n\nWhen device_register() or mtd_nvmem_add() fails inside\nadd_mtd_device() for a partition, the error handling triggers\nmtd_release() via put_device() or device_unregister(). mtd_release()\ncalls release_mtd_partition() which frees the mtd_info structure.\nHowever, callers such as mtd_add_partition() and add_mtd_partitions()\nalso call free_partition() in their error paths, resulting in a double\nfree.\n\nAdditionally, release_mtd_partition() hits WARN_ON(!list_empty(\n&mtd->part.node)) because the partition node is still linked in the\nparent's partitions list when the release callback fires from the\nadd_mtd_device() error path.\n\nFix this by overriding dev->type and dev->release before put_device()\nin the error paths, so that device_release() invokes a no-op function\ninstead of mtd_release(). For the mtd_nvmem_add() failure case,\ndevice_unregister() is replaced with device_del() to separate the\ndevice removal from the final kobject reference drop, allowing the\noverride to take effect before put_device() is called.\n\nThe callers' error paths (list_del + free_partition) remain the sole\nowners of mtd_info lifetime on add_mtd_device() failure, which is the\nexpected contract.\n\nThe normal partition teardown path is not affected: del_mtd_device()\ngoes through kref_put() -> mtd_device_release() -> device_unregister()\nwith dev->type still set to &mtd_devtype, so mtd_release() ->\nrelease_mtd_partition() continues to work correctly for the regular\nremoval case."
}
],
"lastModified": "2026-08-17T06:17:50.600",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}