Menu

Star on GitHub · 3.2k

CVE-2023-53311

7.8 · HIGH

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…

Published Sep 16, 2025CWE-416EPSS 0.16%

Overview

CVE-2023-53311 is a high-severity vulnerability. It was published on September 16, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

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 a

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2023-53311?

CVE-2023-53311 is a high-severity vulnerability. It was published on September 16, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2023-53311?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2023-53311?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2023-53311?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2023-53311 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2023

View all