Kernel warning via stale F2FS dentry cache
Published Jan 13, 2026 · Updated Jan 13, 2026
Filesystem state inconsistency in affected Linux Kernel releases allows local users to trigger a kernel warning through crafted F2FS renames. In f2fs_rename, a failed f2fs_add_link call leaves committed directory changes paired with stale VFS dentries that reference an inode whose link count is already zero. The prerequisite is administrative control to mount a corrupted F2FS image and issue the required rename sequence; published evidence reports a drop_nlink warning, not a crash or broader service interruption.
Summary
What happened
Filesystem state inconsistency in affected Linux Kernel releases allows local users to trigger a kernel warning through crafted F2FS renames. In f2fs_rename, a failed f2fs_add_link call leaves committed directory changes paired with stale VFS dentries that reference an inode whose link count is already zero. The prerequisite is administrative control to mount a corrupted F2FS image and issue the required rename sequence; published evidence reports a drop_nlink warning, not a crash or broader service interruption.
The record
- CVE
- CVE-2025-71069
- Published
- Jan 13, 2026
- Updated
- Jan 13, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jan 13, 2026CVE publishedPublication date reported by the CVE source.
- Jan 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.2
- Affected versionversion=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <0dde30753c1e8648665dbe069d814e540ce2fd37
- Affected versionversion=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <3d65e27e57aaa9d66709fda4cbfb62a87c04a3f5
- Affected versionversion=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <64587ab4d1f16fc94f70e04fa87b2e3f69f8a7bb
- Affected versionversion=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <c89845fae250efdd59c1d4ec60e9e1c652cee4b6
- Affected versionversion=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <d33f89b34aa313f50f9a512d58dd288999f246b0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo