CVE-2023-53804
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-09

Last updated on: 2025-12-09

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix use-after-free bug of nilfs_root in nilfs_evict_inode() During unmount process of nilfs2, nothing holds nilfs_root structure after nilfs2 detaches its writer in nilfs_detach_log_writer(). However, since nilfs_evict_inode() uses nilfs_root for some cleanup operations, it may cause use-after-free read if inodes are left in "garbage_list" and released by nilfs_dispose_list() at the end of nilfs_detach_log_writer(). Fix this issue by modifying nilfs_evict_inode() to only clear inode without additional metadata changes that use nilfs_root if the file system is degraded to read-only or the writer is detached.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-09
Last Modified
2025-12-09
Generated
2026-05-07
AI Q&A
2025-12-09
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :

The vulnerability can cause use-after-free reads during the unmount process of the nilfs2 file system, potentially leading to system instability, crashes, or memory corruption. This could affect system reliability and security if exploited.


Can you explain this vulnerability to me?

This vulnerability is a use-after-free bug in the Linux kernel's nilfs2 file system. During the unmount process, the nilfs_root structure is freed after detaching its writer, but some cleanup operations still try to use nilfs_root, which can lead to accessing freed memory. This happens if inodes remain in a garbage list and are released during unmount, causing potential memory corruption or crashes.


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, update the Linux kernel to a version where the nilfs2 use-after-free bug in nilfs_evict_inode() has been fixed. This fix involves modifying nilfs_evict_inode() to avoid use-after-free by only clearing the inode without additional metadata changes when the file system is degraded or the writer is detached. Until the update is applied, avoid unmounting nilfs2 file systems under conditions that may trigger this bug.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart