CVE-2023-53311nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput
- 7.8HighCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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 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.
Timeline
ID reserved
By Linux
Published
- 11 months later
· 11 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| CISA-ADPADP (enrichment) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 – < 11afd67f1b3c28eb216e50a3ca8dbcb69bb71793
- affected 0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 – < a3c3b4cbf9b8554120fb230e6516e980c6277487
- affected 0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 – < d2c539c216cce74837a9cf5804eb205939b82227
- affected 0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 – < 37207240872456fbab44a110bde6640445233963
- affected 0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 – < 3645510cf926e6af2f4d44899370d7e5331c93bd
- affected 0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 – < 7532ff6edbf5242376b24a95a2fefb59bb653e5a
- affected 0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 – < 5828d5f5dc877dcfdd7b23102e978e2ecfd86d82
- affected 0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 – < f8654743a0e6909dc634cbfad6db6816f10f3399
- affected 4.0
- unaffected < 4.0
- unaffected 4.14.323 – ≤ 4.14.*
- unaffected 4.19.292 – ≤ 4.19.*
- unaffected 5.4.254 – ≤ 5.4.*
- unaffected 5.10.191 – ≤ 5.10.*
- unaffected 5.15.127 – ≤ 5.15.*
- unaffected 6.1.46 – ≤ 6.1.*
- unaffected 6.4.11 – ≤ 6.4.*
- unaffected 6.5 – ≤ *
References
References8
- https://git.kernel.org/stable/c/11afd67f1b3c28eb216e50a3ca8dbcb69bb71793 (opens in a new tab)
- https://git.kernel.org/stable/c/a3c3b4cbf9b8554120fb230e6516e980c6277487 (opens in a new tab)
- https://git.kernel.org/stable/c/d2c539c216cce74837a9cf5804eb205939b82227 (opens in a new tab)
- https://git.kernel.org/stable/c/37207240872456fbab44a110bde6640445233963 (opens in a new tab)
- https://git.kernel.org/stable/c/3645510cf926e6af2f4d44899370d7e5331c93bd (opens in a new tab)
- https://git.kernel.org/stable/c/7532ff6edbf5242376b24a95a2fefb59bb653e5a (opens in a new tab)
- https://git.kernel.org/stable/c/5828d5f5dc877dcfdd7b23102e978e2ecfd86d82 (opens in a new tab)
- https://git.kernel.org/stable/c/f8654743a0e6909dc634cbfad6db6816f10f3399 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2023-59950 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2023-53311)Record last updated .