f2fs: limit recovery filename logging to stored length
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f356fe0cba0e3523e538987916bd2acedd4e6f41 · < 35c5abccd0924b02ad34126f562d93c8d75b0831| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
F2FS recovery code prints filenames from a buffer that is not NUL-terminated. During recovery logging of a 255-byte filename, it can read past the buffer into other raw inode fields. The input does not specify attacker access or user-interaction requirements.
Engineers running Linux kernels with F2FS should check whether their kernel includes the fix; affected versions are not specified.