CVE-2026-23157

{"id": "CVE-2026-23157", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.5, "attackVector": "LOCAL", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 1.8}]}, "published": "2026-02-14T16:15:55.863", "references": [{"url": "https://git.kernel.org/stable/c/0c3666ec188640c20e254011e7adf4464c32ee58", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/4357e02cafabe01c2d737ceb4c4c6382fc2ee10a", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/4e159150a9a56d66d247f4b5510bed46fe58aa1c", "tags": ["Patch"], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/629666d20c7dcd740e193ec0631fdff035b1f7d6", "tags": ["Patch"], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/bb9be3f713652e330df00f3724c18c7a5469e7ac", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-667"}]}], "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: do not strictly require dirty metadata threshold for metadata writepages\n\n[BUG]\nThere is an internal report that over 1000 processes are\nwaiting at the io_schedule_timeout() of balance_dirty_pages(), causing\na system hang and trigger a kernel coredump.\n\nThe kernel is v6.4 kernel based, but the root problem still applies to\nany upstream kernel before v6.18.\n\n[CAUSE]\nFrom Jan Kara for his wisdom on the dirty page balance behavior first.\n\n This cgroup dirty limit was what was actually playing the role here\n because the cgroup had only a small amount of memory and so the dirty\n limit for it was something like 16MB.\n\n Dirty throttling is responsible for enforcing that nobody can dirty\n (significantly) more dirty memory than there's dirty limit. Thus when\n a task is dirtying pages it periodically enters into balance_dirty_pages()\n and we let it sleep there to slow down the dirtying.\n\n When the system is over dirty limit already (either globally or within\n a cgroup of the running task), we will not let the task exit from\n balance_dirty_pages() until the number of dirty pages drops below the\n limit.\n\n So in this particular case, as I already mentioned, there was a cgroup\n with relatively small amount of memory and as a result with dirty limit\n set at 16MB. A task from that cgroup has dirtied about 28MB worth of\n pages in btrfs btree inode and these were practically the only dirty\n pages in that cgroup.\n\nSo that means the only way to reduce the dirty pages of that cgroup is\nto writeback the dirty pages of btrfs btree inode, and only after that\nthose processes can exit balance_dirty_pages().\n\nNow back to the btrfs part, btree_writepages() is responsible for\nwriting back dirty btree inode pages.\n\nThe problem here is, there is a btrfs internal threshold that if the\nbtree inode's dirty bytes are below the 32M threshold, it will not\ndo any writeback.\n\nThis behavior is to batch as much metadata as possible so we won't write\nback those tree blocks and then later re-COW them again for another\nmodification.\n\nThis internal 32MiB is higher than the existing dirty page size (28MiB),\nmeaning no writeback will happen, causing a deadlock between btrfs and\ncgroup:\n\n- Btrfs doesn't want to write back btree inode until more dirty pages\n\n- Cgroup/MM doesn't want more dirty pages for btrfs btree inode\n Thus any process touching that btree inode is put into sleep until\n the number of dirty pages is reduced.\n\nThanks Jan Kara a lot for the analysis of the root cause.\n\n[ENHANCEMENT]\nSince kernel commit b55102826d7d (\"btrfs: set AS_KERNEL_FILE on the\nbtree_inode\"), btrfs btree inode pages will only be charged to the root\ncgroup which should have a much larger limit than btrfs' 32MiB\nthreshold.\nSo it should not affect newer kernels.\n\nBut for all current LTS kernels, they are all affected by this problem,\nand backporting the whole AS_KERNEL_FILE may not be a good idea.\n\nEven for newer kernels I still think it's a good idea to get\nrid of the internal threshold at btree_writepages(), since for most cases\ncgroup/MM has a better view of full system memory usage than btrfs' fixed\nthreshold.\n\nFor internal callers using btrfs_btree_balance_dirty() since that\nfunction is already doing internal threshold check, we don't need to\nbother them.\n\nBut for external callers of btree_writepages(), just respect their\nrequests and write back whatever they want, ignoring the internal\nbtrfs threshold to avoid such deadlock on btree inode dirty page\nbalancing."}, {"lang": "es", "value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta: btrfs: no requerir estrictamente el umbral de metadatos sucios para la escritura de p\u00e1ginas de metadatos [ERROR] Existe un informe interno de que m\u00e1s de 1000 procesos est\u00e1n esperando en el io_schedule_timeout() de balance_dirty_pages(), causando un cuelgue del sistema y desencadenando un volcado de memoria del kernel. El kernel est\u00e1 basado en el kernel v6.4, pero el problema ra\u00edz todav\u00eda se aplica a cualquier kernel upstream anterior a la v6.18. [CAUSA] De Jan Kara por su sabidur\u00eda sobre el comportamiento de balanceo de p\u00e1ginas sucias primero. Este l\u00edmite de suciedad del cgroup era lo que realmente estaba desempe\u00f1ando el papel aqu\u00ed porque el cgroup ten\u00eda solo una peque\u00f1a cantidad de memoria y por lo tanto el l\u00edmite de suciedad para \u00e9l era de aproximadamente 16MB. La limitaci\u00f3n de suciedad es responsable de asegurar que nadie pueda ensuciar (significativamente) m\u00e1s memoria sucia de lo que hay de l\u00edmite de suciedad. As\u00ed, cuando una tarea est\u00e1 ensuciando p\u00e1ginas, entra peri\u00f3dicamente en balance_dirty_pages() y la dejamos dormir all\u00ed para ralentizar el ensuciamiento. Cuando el sistema ya est\u00e1 por encima del l\u00edmite de suciedad (ya sea globalmente o dentro de un cgroup de la tarea en ejecuci\u00f3n), no permitiremos que la tarea salga de balance_dirty_pages() hasta que el n\u00famero de p\u00e1ginas sucias caiga por debajo del l\u00edmite. As\u00ed que en este caso particular, como ya mencion\u00e9, hab\u00eda un cgroup con una cantidad de memoria relativamente peque\u00f1a y como resultado con un l\u00edmite de suciedad establecido en 16MB. Una tarea de ese cgroup ha ensuciado p\u00e1ginas por un valor de aproximadamente 28MB en el inodo btree de btrfs y estas eran pr\u00e1cticamente las \u00fanicas p\u00e1ginas sucias en ese cgroup. As\u00ed que eso significa que la \u00fanica forma de reducir las p\u00e1ginas sucias de ese cgroup es realizar el writeback de las p\u00e1ginas sucias del inodo btree de btrfs, y solo despu\u00e9s de eso esos procesos pueden salir de balance_dirty_pages(). Ahora volviendo a la parte de btrfs, btree_writepages() es responsable de realizar el writeback de las p\u00e1ginas sucias del inodo btree. El problema aqu\u00ed es que hay un umbral interno de btrfs que si los bytes sucios del inodo btree est\u00e1n por debajo del umbral de 32M, no realizar\u00e1 ning\u00fan writeback. Este comportamiento es para agrupar la mayor cantidad posible de metadatos para que no escribamos de vuelta esos bloques de \u00e1rbol y luego los volvamos a copiar en escritura (re-COW) para otra modificaci\u00f3n. Estos 32MiB internos son m\u00e1s altos que el tama\u00f1o de p\u00e1gina sucia existente (28MiB), lo que significa que no se realizar\u00e1 ning\u00fan writeback, causando un interbloqueo entre btrfs y cgroup: - Btrfs no quiere realizar el writeback del inodo btree hasta que haya m\u00e1s p\u00e1ginas sucias - Cgroup/MM no quiere m\u00e1s p\u00e1ginas sucias para el inodo btree de btrfs As\u00ed, cualquier proceso que toque ese inodo btree es puesto a dormir hasta que el n\u00famero de p\u00e1ginas sucias se reduzca. Muchas gracias a Jan Kara por el an\u00e1lisis de la causa ra\u00edz. [MEJORA] Desde el commit del kernel b55102826d7d ('btrfs: establecer AS_KERNEL_FILE en el btree_inode'), las p\u00e1ginas del inodo btree de btrfs solo se cargar\u00e1n al cgroup ra\u00edz, el cual deber\u00eda tener un l\u00edmite mucho mayor que el umbral de 32MiB de btrfs. As\u00ed que no deber\u00eda afectar a kernels m\u00e1s nuevos. Pero para todos los kernels LTS actuales, todos est\u00e1n afectados por este problema, y realizar un backport de todo el AS_KERNEL_FILE puede no ser una buena idea. Incluso para kernels m\u00e1s nuevos, sigo pensando que es una buena idea eliminar el umbral interno en btree_writepages(), ya que en la mayor\u00eda de los casos cgroup/MM tiene una mejor visi\u00f3n del uso de la memoria de todo el sistema que el umbral fijo de btrfs. Para los llamadores internos que usan btrfs_btree_balance_dirty(), ya que esa funci\u00f3n ya est\u00e1 realizando una comprobaci\u00f3n de umbral interna, ---truncado---"}], "lastModified": "2026-03-25T11:16:19.570", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "A25D17E8-22B0-4A6C-B1FD-1EA80C78268F", "versionEndExcluding": "6.18.9", "versionStartIncluding": "2.6.29"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.19:rc1:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "17B67AA7-40D6-4AFA-8459-F200F3D7CFD1"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.19:rc2:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "C47E4CC9-C826-4FA9-B014-7FE3D9B318B2"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.19:rc3:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "F71D92C0-C023-48BD-B3B6-70B638EEE298"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.19:rc4:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "13580667-0A98-40CC-B29F-D12790B91BDB"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.19:rc5:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "CAD1FED7-CF48-47BF-AC7D-7B6FA3C065FC"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.19:rc6:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "3EF854A1-ABB1-4E93-BE9A-44569EC76C0D"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.19:rc7:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "F5DC0CA6-F0AF-4DDF-A882-3DADB9A886A7"}], "operator": "OR"}]}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}