CVE-2026-72477: fs/ntfs3: call _ntfs_bad_inode() when failing to rename
In the Linux kernel, the following vulnerability has been resolved:
fs/ntfs3: call ntfsbadinode() when failing to rename
It is safe to call ntfsbadinode on live inodes since: commit 519b078998ce ("fs/ntfs3: Exclude call makebadinode for live nodes.")
The WARNON was added when it wasn't safe by: commit d99208b91933 ("fs/ntfs3: cancle set bad inode after removing name fails")
Replace the WARNON with a call to ntfsbadinode() to prevent further operations on the inconsistent inode.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-72477?
CVE-2026-72477 has a risk score of 27, indicating a higher level of severity.
How do I fix CVE-2026-72477?
To fix CVE-2026-72477, ensure you update your Linux kernel to the latest patched version that addresses this vulnerability.
What systems are affected by CVE-2026-72477?
CVE-2026-72477 affects systems running vulnerable versions of the Linux kernel that implement the NTFS3 file system.
What is the potential impact of CVE-2026-72477?
The potential impact of CVE-2026-72477 includes issues related to inode handling that may lead to data integrity concerns during renaming operations.
When was CVE-2026-72477 published?
CVE-2026-72477 was published on August 15, 2026.