Linux Kernel up to 6.4.10 nilfs2 nilfs_detach_log_writer use after free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.7$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.4.10. It has been rated as critical. Affected is the function nilfs_detach_log_writer of the component nilfs2. This manipulation causes use after free. The identification of this vulnerability is CVE-2023-53311. There is no exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 6.4.10 and classified as critical. Affected by this vulnerability is the function nilfs_detach_log_writer of the component nilfs2. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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 is to allow for narrowing of such conditions.

It is possible to read the advisory at git.kernel.org. This vulnerability is known as CVE-2023-53311 since 09/16/2025. The exploitation appears to be easy. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 12/27/2025).

The vulnerability scanner Nessus provides a plugin with the ID 265588 (Linux Distros Unpatched Vulnerability : CVE-2023-53311), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.14.323, 4.19.292, 5.4.254, 5.10.191, 5.15.127, 6.1.46 or 6.4.11 eliminates this vulnerability. Applying the patch 11afd67f1b3c28eb216e50a3ca8dbcb69bb71793/a3c3b4cbf9b8554120fb230e6516e980c6277487/d2c539c216cce74837a9cf5804eb205939b82227/37207240872456fbab44a110bde6640445233963/3645510cf926e6af2f4d44899370d7e5331c93bd/7532ff6edbf5242376b24a95a2fefb59bb653e5a/5828d5f5dc877dcfdd7b23102e978e2ecfd86d82/f8654743a0e6909dc634cbfad6db6816f10f3399 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (265588) and CERT Bund (WID-SEC-2025-2077). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • IBM QRadar SIEM
  • SUSE openSUSE
  • Open Source Linux Kernel
  • RESF Rocky Linux
  • Dell Secure Connect Gateway

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.9
VulDB Meta Temp Score: 7.7

VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 7.8
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 265588
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2023-53311

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 4.14.323/4.19.292/5.4.254/5.10.191/5.15.127/6.1.46/6.4.11
Patch: 11afd67f1b3c28eb216e50a3ca8dbcb69bb71793/a3c3b4cbf9b8554120fb230e6516e980c6277487/d2c539c216cce74837a9cf5804eb205939b82227/37207240872456fbab44a110bde6640445233963/3645510cf926e6af2f4d44899370d7e5331c93bd/7532ff6edbf5242376b24a95a2fefb59bb653e5a/5828d5f5dc877dcfdd7b23102e978e2ecfd86d82/f8654743a0e6909dc634cbfad6db6816f10f3399

Timelineinfo

09/16/2025 Advisory disclosed
09/16/2025 +0 days CVE reserved
09/16/2025 +0 days VulDB entry created
12/27/2025 +102 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2023-53311 (🔒)
GCVE (CVE): GCVE-0-2023-53311
GCVE (VulDB): GCVE-100-324499
CERT Bund: WID-SEC-2025-2077 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 09/16/2025 20:34
Updated: 12/27/2025 08:27
Changes: 09/16/2025 20:34 (59), 09/20/2025 20:46 (2), 10/21/2025 05:19 (7), 12/02/2025 00:06 (11), 12/27/2025 08:27 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!