CVE-2026-90261
In the Linux kernel, the following vulnerability has been resolved:
btrfs: zoned: flush active metadata block group at btree_writepages() start
btree_writepages() writes the btree inode's dirty metadata in ascending logical address order. On a zoned filesystem only one metadata and one system block group is active for writing at a time, and check_bg_is_active() (via btrfs_check_meta_write_pointer()) pivots the active block group as writeback moves from one block group to the next.
If the active block group sits at a higher logical address than another block group that also holds dirty metadata, the ascending walk reaches the lower one first and, to write it, has to finish the active block group and activate the lower one.
Leer descripción completaMostrar menos
It cannot finish a block group that still has unsent IO, and during WB_SYNC_ALL && !for_sync (commit) writeback it deliberately refuses to wait for that IO under fs_info->zoned_meta_io_lock, as that can deadlock. The pivot thus cannot issue the submission itself either, so it gives up: btrfs_check_meta_write_pointer() returns -EAGAIN, which btrfs_write_and_wait_transaction() treats as fatal and aborts the transaction, forcing the filesystem read-only. This happens intermittently under metadata-heavy relocation (e.g. fstests btrfs/187).
Flush the active metadata and system block groups at the start of btree_writepages(), under the fs_info->zoned_meta_io_lock it already holds, so they have no unsent IO left and the later pivot can finish them and make forward progress.
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.22%
- Percentil entre todas las CVEs puntuadas: 11
- 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-90261",
"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": "13bb483d32abb6f8ebd40141d87eb68f11cc2dd2",
"lessThan": "e2de2989adb3e58c2320e57c255f52e065667b5e",
"versionType": "git"
},
{
"status": "affected",
"version": "13bb483d32abb6f8ebd40141d87eb68f11cc2dd2",
"lessThan": "ecc05eda9a346848ae01a6c8bfa3f0bec133bd8b",
"versionType": "git"
},
{
"status": "affected",
"version": "fca3a1cd3ba47f1815e0c0fcdc9aafaf02ee0a75",
"versionType": "git"
},
{
"status": "affected",
"version": "6.5.5",
"lessThan": "6.6",
"versionType": "semver"
}
],
"programFiles": [
"fs/btrfs/extent_io.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": "7.2.6",
"versionType": "semver",
"lessThanOrEqual": "7.2.*"
},
{
"status": "unaffected",
"version": "7.3-rc1",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"fs/btrfs/extent_io.c"
],
"defaultStatus": "affected"
}
]
}
],
"published": "2026-09-17T17:17:22.537",
"references": [
{
"url": "https://git.kernel.org/stable/c/e2de2989adb3e58c2320e57c255f52e065667b5e",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/ecc05eda9a346848ae01a6c8bfa3f0bec133bd8b",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"vulnStatus": "Received",
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: zoned: flush active metadata block group at btree_writepages() start\n\nbtree_writepages() writes the btree inode's dirty metadata in ascending\nlogical address order. On a zoned filesystem only one metadata and one\nsystem block group is active for writing at a time, and\ncheck_bg_is_active() (via btrfs_check_meta_write_pointer()) pivots the\nactive block group as writeback moves from one block group to the next.\n\nIf the active block group sits at a higher logical address than another\nblock group that also holds dirty metadata, the ascending walk reaches\nthe lower one first and, to write it, has to finish the active block\ngroup and activate the lower one. It cannot finish a block group that\nstill has unsent IO, and during WB_SYNC_ALL && !for_sync (commit)\nwriteback it deliberately refuses to wait for that IO under\nfs_info->zoned_meta_io_lock, as that can deadlock. The pivot thus cannot\nissue the submission itself either, so it gives up:\nbtrfs_check_meta_write_pointer() returns -EAGAIN, which\nbtrfs_write_and_wait_transaction() treats as fatal and aborts the\ntransaction, forcing the filesystem read-only. This happens\nintermittently under metadata-heavy relocation (e.g. fstests btrfs/187).\n\nFlush the active metadata and system block groups at the start of\nbtree_writepages(), under the fs_info->zoned_meta_io_lock it already\nholds, so they have no unsent IO left and the later pivot can finish\nthem and make forward progress."
}
],
"lastModified": "2026-09-17T17:17:22.537",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}