CVE-2025-21722
nilfs2: do not force clear folio if buffer is referenced
Reported by linux · Published February 27, 2025
In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not force clear folio if buffer is referenced Patch series "nilfs2: protect busy buffer heads from being force-cleared". This series fixes the buffer head state inconsistency issues reported by syzbot that occurs when the filesystem is corrupted and falls back to read-only, and the associated buffer head use-after-free issue. This patch (of 2): Syzbot has reported that after nilfs2 detects filesystem corruption and falls back to read-only, inconsistencies in the buffer state may occur. One of the inconsistencies is that when nilfs2 calls mark_buffer_dirty() to set a data or metadata buffer as dirty, but it detects that the buffer is not in the uptodate state: WARNING: CPU: 0 PID: 6049 at fs/buffer.c:1177 mark_buffer_dirty+0x2e5/0x520 fs/buffer.c:1177 ... Call Trace: <TASK> nilfs_palloc_commit_alloc_entry+0x4b/0x160 fs/nilfs2/alloc.c:598 nilfs_ifile_create_inode+0x1dd/0x3a0 fs/nilfs2/ifile.c:73 nilfs_new_inode+0x254/0x830 fs/nilfs2/inode.c:344 nilfs_mkdir+0x10d/0x340 fs/nilfs2/namei.c:218 vfs_mkdir+0x2f9/0x4f0 fs/namei.c:4257 do_mkdirat+0x264/0x3a0 fs/namei.c:4280 __do_sys_mkdirat fs/namei.c:4295 [inline] __se_sys_mkdirat fs/namei.c:4293 [inline] __x64_sys_mkdirat+0x87/0xa0 fs/namei.c:4293 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f The other is when nilfs_btree_propagate(), which propagates the dirty state to the ancestor nodes of a b-tree that point to a dirty buffer, detects that the origin buffer is not dirty, even though it should be: WARNING: CPU: 0 PID: 5245 at fs/nilfs2/btree.c:2089 nilfs_btree_propagate+0xc79/0xdf0 fs/nilfs2/btree.c:2089 ... Call Trace: <TASK> nilfs_bmap_propagate+0x75/0x120 fs/nilfs2/bmap.c:345 nilfs_collect_file_data+0x4d/0xd0 fs/nilfs2/segment.c:587 nilfs_segctor_apply_buffers+0x184/0x340 fs/nilfs2/segment.c:1006 nilfs_segctor_scan_file+0x28c/0xa50 fs/nilfs2/segment.c:1045 nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1216 [inline] nilfs_segctor_collect fs/nilfs2/segment.c:1540 [inline] nilfs_segctor_do_construct+0x1c28/0x6b90 fs/nilfs2/segment.c:2115 nilfs_segctor_construct+0x181/0x6b0 fs/nilfs2/segment.c:2479 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2587 [inline] nilfs_segctor_thread+0x69e/0xe80 fs/nilfs2/segment.c:2701 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK> Both of these issues are caused by the callbacks that handle the page/folio write requests, forcibly clear various states, including the working state of the buffers they hold, at unexpected times when they detect read-only fallback. Fix these issues by checking if the buffer is referenced before clearing the page/folio state, and skipping the clear if it is.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel-tools | Amazon Linux | 4.14.355-277.647.amzn2 |
| python-perf | Amazon Linux | 4.14.355-277.647.amzn2 |
| kernel-headers | Amazon Linux | 4.14.355-277.647.amzn2 |
| kernel-tools-devel | Amazon Linux | 4.14.355-277.647.amzn2 |
| kernel-devel | Amazon Linux | 4.14.355-277.647.amzn2 |
| kernel | Amazon Linux | 4.14.355-277.647.amzn2 |
| linux_kernel | linux | 6.13.2, 6.12.13, 6.1.129, 5.15.179, 5.10.235, 5.4.291 |
| Linux | Linux | f51ff43c4c5a6c8e72d0aca89e4d5e688938412f, 8458c686d50a804611b97038dd6e75a474ac2221, 7d0544bacc11d6aa26ecd7debf9353193c7a3328, 557ccf5e49f1fb848a29698585bcab2e50a597ef, 1098bb8d52419d262a3358d099a1598a920b730f |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 8c26c4e2694a163d525976e804d81cd955bbb40c, 8c26c4e2694a163d525976e804d81cd955bbb40c, 8c26c4e2694a163d525976e804d81cd955bbb40c |
| Linux | Linux | 3.10, 0, 5.4.291 |
| amazon:2 | kernel-tools | 0 |
| amazon:2 | python-perf | 0 |
| amazon:2 | kernel-headers | 0 |
| amazon:2 | kernel-tools-devel | 0 |
| amazon:2 | kernel-devel | 0 |
| amazon:2 | kernel | 0 |
| Linux | Linux | 6.6.160, 5.10.235, 5.15.179 |
| amazon:2 | kernel-livepatch-4.14.355-277.647 | 0 |
| linux | linux_kernel | 3.10, 3.10, 3.10 |
| amazon:2 | perf | 0 |
Timeline
- Feb 26, 2025 CVE Published
- Feb 27, 2025 EPSS Score (30 in total, the first dated here)
- Mar 19, 2025 Coalition ESS Score (12 in total, the first dated here)
- Dec 22, 2025 Security Advisory (409 in total, the first dated here)
- Jan 14, 2026 PoC Published
- Apr 20, 2026 Distribution Patch (364 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-21722
vulnetix vdb fixes CVE-2025-21722
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-21722/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart