+5
−4
Loading
Only plain data whose start position and on-disk physical length are both aligned to the block size should be classified as interlaced plain extents. Otherwise, it must be treated as shifted plain extents. This issue was found by syzbot using a crafted compressed image containing plain extents with unaligned physical lengths, which can cause OOB read in z_erofs_transform_plain(). Reported-and-tested-by:<syzbot+d988dc155e740d76a331@syzkaller.appspotmail.com> Closes: https://lore.kernel.org/r/699d5714.050a0220.cdd3c.03e7.GAE@google.com Fixes: 1d191b4c ("erofs: implement encoded extent metadata") Signed-off-by:
Gao Xiang <hsiangkao@linux.alibaba.com>