CVE-2025-21721: nilfs2: handle errors that nilfs_prepare_chunk() may return
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: handle errors that nilfspreparechunk() may return
Patch series "nilfs2: fix issues with rename operations".
This series fixes BUGON check failures reported by syzbot around rename operations, and a minor behavioral issue where the mtime of a child directory changes when it is renamed instead of moved.
This patch (of 2):
The directory manipulation routines nilfssetlink() and nilfsdeleteentry() rewrite the directory entry in the folio/page previously read by nilfsfindentry(), so error handling is omitted on the assumption that nilfspreparechunk(), which prepares the buffer for rewriting, will always succeed for these. And if an error is returned, it triggers the legacy BUGON() checks in each routine.
This assumption is wrong, as proven by syzbot: the buffer layer called by nilfspreparechunk() may call nilfsgetblock() if necessary, which may fail due to metadata corruption or other reasons. This has been there all along, but improved sanity checks and error handling may have made it more reproducible in fuzzing tests.
Fix this issue by adding missing error paths in nilfssetlink(), nilfsdeleteentry(), and their caller nilfsrename().
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-21721?
CVE-2025-21721 is categorized as a medium severity vulnerability in the Linux kernel.
How do I fix CVE-2025-21721?
To fix CVE-2025-21721, update your Linux kernel to the latest stable version that includes the patch for this vulnerability.
What components are affected by CVE-2025-21721?
CVE-2025-21721 affects multiple versions of the Linux kernel, specifically those between versions 2.6.30 and 6.13.2.
What type of issue does CVE-2025-21721 address?
CVE-2025-21721 addresses errors related to rename operations in the nilfs2 file system within the Linux kernel.
Is there a workaround for CVE-2025-21721?
There is no published workaround for CVE-2025-21721; applying the appropriate kernel patch is recommended.