Re: [PATCH] fs/adfs: bound directory entry name length in adfs_fplus_getnext()
From: Christian Brauner
Date: Thu Nov 05 2026 - 16:39:25 EST
On Wed, 15 Jul 2026 20:52:31 +0900, HyeongJun An wrote:
> adfs_fplus_getnext() reads the per-entry name length bigdirobnamelen
> straight from the on-disk big directory and passes it to
> adfs_dir_copyfrom() as the copy length into obj->name[], a fixed
> ADFS_MAX_NAME_LEN (260) byte buffer. adfs_dir_copyfrom() only bounds
> the copy against the number of directory buffers, not the size of the
> destination, so a crafted image with bigdirobnamelen larger than the
> buffer overflows the stack-allocated object_info::name that
> adfs_fplus_iterate() passes in.
>
> [...]
Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.fixes branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.fixes
[1/1] fs/adfs: bound directory entry name length in adfs_fplus_getnext()
https://git.kernel.org/vfs/vfs/c/8b41fb1fc25d