CVE-2025-40150
Full vulnerability record from the local CVENow database.
Description
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid migrating empty section It reports a bug from device w/ zufs: F2FS-fs (dm-64): Inconsistent segment (173822) type [1, 0] in SSA and SIT F2FS-fs (dm-64): Stopped filesystem due to reason: 4 Thread A Thread B - f2fs_expand_inode_data - f2fs_allocate_pinning_section - f2fs_gc_range - do_garbage_collect w/ segno #x - writepage - f2fs_allocate_data_block - new_curseg - allocate segno #x The root cause is: fallocate on pinning file may race w/ block allocation as above, result in do_garbage_collect() from fallocate() may migrate segment which is just allocated by a log, the log will update segment type in its in-memory structure, however GC will get segment type from on-disk SSA block, once segment type changes by log, we can detect such inconsistency, then shutdown filesystem. In this case, on-disk SSA shows type of segno #173822 is 1 (SUM_TYPE_NODE), however segno #173822 was just allocated as data type segment, so in-memory SIT shows type of segno #173822 is 0 (SUM_TYPE_DATA). Change as below to fix this issue: - check whether current section is empty before gc - add sanity checks on do_garbage_collect() to avoid any race case, result in migrating segment used by log. - btw, it fixes misc issue in printed logs: "SSA and SIT" -> "SIT and SSA".
View original CVE JSON
{
"id": "CVE-2025-40150",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-11-12T11:15:44.923",
"lastModified": "2026-10-19T21:10:00.160",
"vulnStatus": "Deferred",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to avoid migrating empty section\n\nIt reports a bug from device w/ zufs:\n\nF2FS-fs (dm-64): Inconsistent segment (173822) type [1, 0] in SSA and SIT\nF2FS-fs (dm-64): Stopped filesystem due to reason: 4\n\nThread A\t\t\t\tThread B\n- f2fs_expand_inode_data\n - f2fs_allocate_pinning_section\n - f2fs_gc_range\n - do_garbage_collect w/ segno #x\n\t\t\t\t\t- writepage\n\t\t\t\t\t - f2fs_allocate_data_block\n\t\t\t\t\t - new_curseg\n\t\t\t\t\t - allocate segno #x\n\nThe root cause is: fallocate on pinning file may race w/ block allocation\nas above, result in do_garbage_collect() from fallocate() may migrate\nsegment which is just allocated by a log, the log will update segment type\nin its in-memory structure, however GC will get segment type from on-disk\nSSA block, once segment type changes by log, we can detect such\ninconsistency, then shutdown filesystem.\n\nIn this case, on-disk SSA shows type of segno #173822 is 1 (SUM_TYPE_NODE),\nhowever segno #173822 was just allocated as data type segment, so in-memory\nSIT shows type of segno #173822 is 0 (SUM_TYPE_DATA).\n\nChange as below to fix this issue:\n- check whether current section is empty before gc\n- add sanity checks on do_garbage_collect() to avoid any race case, result\nin migrating segment used by log.\n- btw, it fixes misc issue in printed logs: \"SSA and SIT\" -> \"SIT and SSA\"."
},
{
"lang": "es",
"value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\nf2fs: arreglo para evitar migrar una sección vacía\n\nReporta un error desde un dispositivo con zufs:\n\nF2FS-fs (dm-64): Tipo de segmento inconsistente (173822) [1, 0] en SSA y SIT\nF2FS-fs (dm-64): Sistema de archivos detenido debido a la razón: 4\n\nHilo A\t\t\t\tHilo B\n- f2fs_expand_inode_data\n - f2fs_allocate_pinning_section\n - f2fs_gc_range\n - do_garbage_collect con segno #x\n\t\t\t\t\t- writepage\n\t\t\t\t\t - f2fs_allocate_data_block\n\t\t\t\t\t - new_curseg\n\t\t\t\t\t - allocate segno #x\n\nLa causa raíz es: fallocate en un archivo de anclaje puede competir con la asignación de bloques como se describe anteriormente, lo que resulta en que do_garbage_collect() desde fallocate() puede migrar un segmento que acaba de ser asignado por un registro; el registro actualizará el tipo de segmento en su estructura en memoria, sin embargo, el GC obtendrá el tipo de segmento del bloque SSA en disco; una vez que el tipo de segmento cambie por el registro, podemos detectar dicha inconsistencia y luego apagar el sistema de archivos.\n\nEn este caso, el SSA en disco muestra que el tipo de segno #173822 es 1 (SUM_TYPE_NODE), sin embargo, el segno #173822 acababa de ser asignado como un segmento de tipo de datos, por lo que el SIT en memoria muestra que el tipo de segno #173822 es 0 (SUM_TYPE_DATA).\n\nCambio como se detalla a continuación para solucionar este problema:\n- verificar si la sección actual está vacía antes del gc\n- añadir comprobaciones de cordura en do_garbage_collect() para evitar cualquier caso de carrera, lo que resulta en la migración de un segmento utilizado por el registro.\n- por cierto, soluciona un problema misceláneo en los registros impresos: “SSA y SIT” -> “SIT y SSA”."
}
],
"affected": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"affectedData": [
{
"vendor": "Linux",
"product": "Linux",
"defaultStatus": "unaffected",
"programFiles": [
"fs/f2fs/gc.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"versions": [
{
"version": "40d76c393cca83938b11eb7ca8983aa3cd0ed69b",
"lessThan": "db489778e6f2a4034c2cd26fadda2796eba24dcd",
"versionType": "git",
"status": "affected"
},
{
"version": "9703d69d9d153bb230711d0d577454552aeb13d4",
"lessThan": "25d2dc669f2a7e48b335d1cb07139f2ffc9fe5df",
"versionType": "git",
"status": "affected"
},
{
"version": "9703d69d9d153bb230711d0d577454552aeb13d4",
"lessThan": "eec1589be36fcf7440755703e4faeee2c01e360b",
"versionType": "git",
"status": "affected"
},
{
"version": "9703d69d9d153bb230711d0d577454552aeb13d4",
"lessThan": "d625a2b08c089397d3a03bff13fa8645e4ec7a01",
"versionType": "git",
"status": "affected"
},
{
"version": "6.6.33",
"lessThan": "6.6.130",
"versionType": "semver",
"status": "affected"
}
]
},
{
"vendor": "Linux",
"product": "Linux",
"defaultStatus": "affected",
"programFiles": [
"fs/f2fs/gc.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"versions": [
{
"version": "6.9",
"status": "affected"
},
{
"version": "0",
"lessThan": "6.9",
"versionType": "semver",
"status": "unaffected"
},
{
"version": "6.6.130",
"lessThanOrEqual": "6.6.*",
"versionType": "semver",
"status": "unaffected"
},
{
"version": "6.12.78",
"lessThanOrEqual": "6.12.*",
"versionType": "semver",
"status": "unaffected"
},
{
"version": "6.17.3",
"lessThanOrEqual": "6.17.*",
"versionType": "semver",
"status": "unaffected"
},
{
"version": "6.18",
"lessThanOrEqual": "*",
"versionType": "original_commit_for_fix",
"status": "unaffected"
}
]
}
]
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/25d2dc669f2a7e48b335d1cb07139f2ffc9fe5df",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/d625a2b08c089397d3a03bff13fa8645e4ec7a01",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/db489778e6f2a4034c2cd26fadda2796eba24dcd",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/eec1589be36fcf7440755703e4faeee2c01e360b",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}