CVE-2026-89838
f2fs: limit recovery filename logging to stored length
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.112, 6.18.53, 7.2.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: f2fs: limit recovery filename logging to stored length F2FS stores recovery filenames as a length plus a fixed-size i_name buffer. The buffer is not NUL-terminated, but recover_inode() and recover_dentry() print it with %s. For a 255-byte filename, recovery logging can read past i_name into the following raw inode fields. Print the name with a precision bounded by i_namelen and F2FS_NAME_LEN.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
3.11
- KernelLinux
From 3.11.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.53; From 6.19.0 · fixed in 7.2.5
References 8
git.kernel.org
- stable/c/b8ac8b14b9d92dd2e1cb05fa8994f41f701fbf28
- stable/c/450ab2e5dbe0ef6e3ed73214256565f6f003d62a
- stable/c/3d02c7c8446f5d6793ac67f93bf3f84bf24e3f25
- stable/c/e754120f8ede55cc773ade108cf7e5b17c859c46
- stable/c/7ab1780074943508534343e1e5e5ab0c9ef9dd7b
- stable/c/35c5abccd0924b02ad34126f562d93c8d75b0831
- stable/c/317d32e1a8deaf1c01c388badc667334c39e62ca
- stable/c/01027b2fcb74dade59fb833b51023f6593b6a9a2