Към съдържанието
Търсене

CVE-2026-23157: Linux

Няма оценка

CVSS

Няма данни

Вероятност да бъде експлоатирана в следващите 30 дни (EPSS)

Няма потвърждение

Атакува се

Няма данни

Време до експлоатация

    Описание

    Оригинално описание

    In the Linux kernel, the following vulnerability has been resolved: btrfs: do not strictly require dirty metadata threshold for metadata writepages [BUG] There is an internal report that over 1000 processes are waiting at the io_schedule_timeout() of balance_dirty_pages(), causing a system hang and trigger a kernel coredump. The kernel is v6.4 kernel based, but the root problem still applies to any upstream kernel before v6.18. [CAUSE] From Jan Kara for his wisdom on the dirty page balance behavior first. This cgroup dirty limit was what was actually playing the role here because the cgroup had only a small amount of memory and so the dirty limit for it was something like 16MB. Dirty throttling is responsible for enforcing that nobody can dirty (significantly) more dirty memory than there's dirty limit. Thus when a task is dirtying pages it periodically enters into balance_dirty_pages() and we let it sleep there to slow down the dirtying. When the system is over dirty limit already (either globally or within a cgroup of the running task), we will not let the task exit from balance_dirty_pages() until the number of dirty pages drops below the limit. So in this particular case, as I already mentioned, there was a cgroup with relatively small amount of memory and as a result with dirty limit set at 16MB. A task from that cgroup has dirtied about 28MB worth of pages in btrfs btree inode and these were practically the only dirty pages in that cgroup. So that means the only way to reduce the dirty pages of that cgroup is to writeback the dirty pages of btrfs btree inode, and only after that those processes can exit balance_dirty_pages(). Now back to the btrfs part, btree_writepages() is responsible for writing back dirty btree inode pages. The problem here is, there is a btrfs internal threshold that if the btree inode's dirty bytes are below the 32M threshold, it will not do any writeback. This behavior is to batch as much meta

    Засегнати продукти

    • Linux Linux: 793955bca66c99defdffc857ae6eb7e8431d6bbe преди 6a8b6242eaa1dd7a0de2d6de6420d10ffe68db90; 793955bca66c99defdffc857ae6eb7e8431d6bbe преди bb9be3f713652e330df00f3724c18c7a5469e7ac; 793955bca66c99defdffc857ae6eb7e8431d6bbe преди 4357e02cafabe01c2d737ceb4c4c6382fc2ee10a; 793955bca66c99defdffc857ae6eb7e8431d6bbe преди 0c3666ec188640c20e254011e7adf4464c32ee58; 793955bca66c99defdffc857ae6eb7e8431d6bbe преди 629666d20c7dcd740e193ec0631fdff035b1f7d6; 793955bca66c99defdffc857ae6eb7e8431d6bbe преди 4e159150a9a56d66d247f4b5510bed46fe58aa1c
    • Linux Linux: 2.6.29; преди 2.6.29; 5.15.209 до 5.15.*; 6.1.167 до 6.1.*; 6.6.130 до 6.6.*; 6.12.78 до 6.12.*; 6.18.9 до 6.18.*; от 6.19 нататък
    • Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem: всички версии

    История

    • 14 февруари 2026 Публикувано

    Други уязвимости в Linux Linux

    Първоизточници

    CVE-2026-23157: Linux | freedomonline.bg