CVE-2023-53311
published 2025-09-16CVE-2023-53311: In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput During unmount process…
PriorityP340high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.15%
4.6th percentile
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput
During unmount process of nilfs2, nothing holds nilfs_root structure after
nilfs2 detaches its writer in nilfs_detach_log_writer(). Previously,
nilfs_evict_inode() could cause use-after-free read for nilfs_root if
inodes are left in "garbage_list" and released by nilfs_dispose_list at
the end of nilfs_detach_log_writer(), and this bug was fixed by commit
9b5a04ac3ad9 ("nilfs2: fix use-after-free bug of nilfs_root in
nilfs_evict_inode()").
However, it turned out that there is another possibility of UAF in the
call path where mark_inode_dirty_sync() is called from iput():
nilfs_detach_log_writer()
nilfs_dispose_list()
iput()
mark_inode_dirty_sync()
__mark_inode_dirty()
nilfs_dirty_inode()
__nilfs_mark_inode_dirty()
nilfs_load_inode_block() --> causes UAF of nilfs_root struct
This can happen after commit 0ae45f63d4ef ("vfs: add support for a
lazytime mount option"), which changed iput() to call
mark_inode_dirty_sync() on its final reference if i_state has I_DIRTY_TIME
flag and i_nlink is non-zero.
This issue appears after commit 28a65b49eb53 ("nilfs2: do not write dirty
data after degenerating to read-only") when using the syzbot reproducer,
but the issue has potentially existed before.
Fix this issue by adding a "purging flag" to the nilfs structure, setting
that flag while disposing the "garbage_list" and checking it in
__nilfs_mark_inode_dirty().
Unlike commit 9b5a04ac3ad9 ("nilfs2: fix use-after-free bug of nilfs_root
in nilfs_evict_inode()"), this patch does not rely on ns_writer to
determine whether to skip operations, so as not to break recovery on
mount. The nilfs_salvage_orphan_logs routine dirties the buffer of
salvaged data before attaching the log writer, so changing
__nilfs_mark_inode_dirty() to skip the operation when ns_writer is NULL
will cause recovery write to fail. The purpose of using the cleanup-only
flag
Affected
22 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.52-1 (bookworm) | linux 6.1.52-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 < 11afd67f1b3c28eb216e50a3ca8dbcb69bb71793 | 11afd67f1b3c28eb216e50a3ca8dbcb69bb71793 |
| linux | linux | >= 0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 < a3c3b4cbf9b8554120fb230e6516e980c6277487 | a3c3b4cbf9b8554120fb230e6516e980c6277487 |
| linux | linux | >= 0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 < d2c539c216cce74837a9cf5804eb205939b82227 | d2c539c216cce74837a9cf5804eb205939b82227 |
| linux | linux | >= 0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 < 37207240872456fbab44a110bde6640445233963 | 37207240872456fbab44a110bde6640445233963 |
| linux | linux | >= 0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 < 3645510cf926e6af2f4d44899370d7e5331c93bd | 3645510cf926e6af2f4d44899370d7e5331c93bd |
| linux | linux | >= 0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 < 7532ff6edbf5242376b24a95a2fefb59bb653e5a | 7532ff6edbf5242376b24a95a2fefb59bb653e5a |
| linux | linux | >= 0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 < 5828d5f5dc877dcfdd7b23102e978e2ecfd86d82 | 5828d5f5dc877dcfdd7b23102e978e2ecfd86d82 |
| linux | linux | >= 0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 < f8654743a0e6909dc634cbfad6db6816f10f3399 | f8654743a0e6909dc634cbfad6db6816f10f3399 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.191-1 | 5.10.191-1 |
| linux | linux_kernel | >= 0 < 6.1.52-1 | 6.1.52-1 |
| linux | linux_kernel | >= 0 < 6.4.11-1 | 6.4.11-1 |
| linux | linux_kernel | >= 0 < 6.4.11-1 | 6.4.11-1 |
| linux | linux_kernel | >= 4.0 < 4.14.323 | 4.14.323 |
| linux | linux_kernel | >= 4.15 < 4.19.292 | 4.19.292 |
| linux | linux_kernel | >= 4.20 < 5.4.254 | 5.4.254 |
| linux | linux_kernel | >= 5.11 < 5.15.127 | 5.15.127 |
| linux | linux_kernel | >= 5.16 < 6.1.46 | 6.1.46 |
| linux | linux_kernel | >= 5.5 < 5.10.191 | 5.10.191 |
| linux | linux_kernel | >= 6.2 < 6.4.11 | 6.4.11 |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.8HIGH
vendor_debian7.8HIGH
vendor_redhat7.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput
vendor_redhat·2025-09-16·CVSS 7.8
CVE-2023-53311 [HIGH] kernel: nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput
kernel: nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput
During unmount process of nilfs2, nothing holds nilfs_root structure after
nilfs2 detaches its writer in nilfs_detach_log_writer(). Previously,
nilfs_evict_inode() could cause use-after-free read for nilfs_root if
inodes are left in "garbage_list" and released by nilfs_dispose_list at
the end of nilfs_detach_log_writer(), and this bug was fixed by commit
9b5a04ac3ad9 ("nilfs2: fix use-after-free bug of nilfs_root in
nilfs_evict_inode()").
However, it turned out that there is another possibility of UAF in the
call path where mark_inode_dirty_sync() is called from iput():
nilfs_de
Debian
CVE-2023-53311: linux - In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix...
vendor_debian·2023·CVSS 7.8
CVE-2023-53311 [HIGH] CVE-2023-53311: linux - In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix...
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput During unmount process of nilfs2, nothing holds nilfs_root structure after nilfs2 detaches its writer in nilfs_detach_log_writer(). Previously, nilfs_evict_inode() could cause use-after-free read for nilfs_root if inodes are left in "garbage_list" and released by nilfs_dispose_list at the end of nilfs_detach_log_writer(), and this bug was fixed by commit 9b5a04ac3ad9 ("nilfs2: fix use-after-free bug of nilfs_root in nilfs_evict_inode()"). However, it turned out that there is another possibility of UAF in the call path where mark_inode_dirty_sync() is called from iput(): nilfs_detach_log_writer() nilfs_dispose_list() iput() mark_inode_dirty_sync() __mark_i
OSV
CVE-2023-53311: In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput During unmoun
osv·2025-09-16·CVSS 7.8
CVE-2023-53311 [HIGH] CVE-2023-53311: In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput During unmoun
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput During unmount process of nilfs2, nothing holds nilfs_root structure after nilfs2 detaches its writer in nilfs_detach_log_writer(). Previously, nilfs_evict_inode() could cause use-after-free read for nilfs_root if inodes are left in "garbage_list" and released by nilfs_dispose_list at the end of nilfs_detach_log_writer(), and this bug was fixed by commit 9b5a04ac3ad9 ("nilfs2: fix use-after-free bug of nilfs_root in nilfs_evict_inode()"). However, it turned out that there is another possibility of UAF in the call path where mark_inode_dirty_sync() is called from iput(): nilfs_detach_log_writer() nilfs_dispose_list() iput() mark_inode_dirty_sync() __mark_i
GHSA
GHSA-53rx-6x56-6g2f: In the Linux kernel, the following vulnerability has been resolved:
nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput
During unmo
ghsa_unreviewed·2025-09-16
CVE-2023-53311 [HIGH] CWE-416 GHSA-53rx-6x56-6g2f: In the Linux kernel, the following vulnerability has been resolved:
nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput
During unmo
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput
During unmount process of nilfs2, nothing holds nilfs_root structure after
nilfs2 detaches its writer in nilfs_detach_log_writer(). Previously,
nilfs_evict_inode() could cause use-after-free read for nilfs_root if
inodes are left in "garbage_list" and released by nilfs_dispose_list at
the end of nilfs_detach_log_writer(), and this bug was fixed by commit
9b5a04ac3ad9 ("nilfs2: fix use-after-free bug of nilfs_root in
nilfs_evict_inode()").
However, it turned out that there is another possibility of UAF in the
call path where mark_inode_dirty_sync() is called from iput():
nilfs_detach_log_writer()
nilfs_dispose_list()
iput()
mark_inode_dirty_sync()
__ma
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/11afd67f1b3c28eb216e50a3ca8dbcb69bb71793https://git.kernel.org/stable/c/3645510cf926e6af2f4d44899370d7e5331c93bdhttps://git.kernel.org/stable/c/37207240872456fbab44a110bde6640445233963https://git.kernel.org/stable/c/5828d5f5dc877dcfdd7b23102e978e2ecfd86d82https://git.kernel.org/stable/c/7532ff6edbf5242376b24a95a2fefb59bb653e5ahttps://git.kernel.org/stable/c/a3c3b4cbf9b8554120fb230e6516e980c6277487https://git.kernel.org/stable/c/d2c539c216cce74837a9cf5804eb205939b82227https://git.kernel.org/stable/c/f8654743a0e6909dc634cbfad6db6816f10f3399
2025-09-16
Published