CVE-2026-89831
In the Linux kernel, the following vulnerability has been resolved:
f2fs: protect critical_task_priority updates with s_umount
The sysfs store path already takes s_umount for GC thread control entries, and ckpt_thread_ioprio is covered as well.
critical_task_priority also updates checkpoint or GC kthread scheduling state, but it is not covered by that serialization. It can race with remount or teardown paths that are stopping those threads.
Protect critical_task_priority sysfs writes with s_umount too.
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.20%
- Percentil entre todas las CVEs puntuadas: 9
- Fecha de la puntuación: 5/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
JSON original (NVD)
Mostrar
{
"id": "CVE-2026-89831",
"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": "52190933c37a96164b271f3f30c16099d9eb8c09",
"lessThan": "bee6dfcc111b1dffdb3e13d73b7028b699fa0165",
"versionType": "git"
},
{
"status": "affected",
"version": "52190933c37a96164b271f3f30c16099d9eb8c09",
"lessThan": "8e4692c6c165e81b2cbb847d8da4b45a53483b33",
"versionType": "git"
}
],
"programFiles": [
"fs/f2fs/sysfs.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "7.0"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "7.0",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "7.2.5",
"versionType": "semver",
"lessThanOrEqual": "7.2.*"
},
{
"status": "unaffected",
"version": "7.3-rc1",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"fs/f2fs/sysfs.c"
],
"defaultStatus": "affected"
}
]
}
],
"published": "2026-09-16T11:16:49.870",
"references": [
{
"url": "https://git.kernel.org/stable/c/8e4692c6c165e81b2cbb847d8da4b45a53483b33",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/bee6dfcc111b1dffdb3e13d73b7028b699fa0165",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"vulnStatus": "Received",
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: protect critical_task_priority updates with s_umount\n\nThe sysfs store path already takes s_umount for GC thread control\nentries, and ckpt_thread_ioprio is covered as well.\n\ncritical_task_priority also updates checkpoint or GC kthread scheduling\nstate, but it is not covered by that serialization. It can race with\nremount or teardown paths that are stopping those threads.\n\nProtect critical_task_priority sysfs writes with s_umount too."
}
],
"lastModified": "2026-09-16T11:16:49.870",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}