summaryrefslogtreecommitdiffstats
path: root/fs/adfs
diff options
context:
space:
mode:
authorTheodore Ts'o <tytso@mit.edu>2023-05-12 15:11:02 -0400
committerTheodore Ts'o <tytso@mit.edu>2023-05-13 18:05:05 -0400
commit2220eaf90992c11d888fe771055d4de330385f01 (patch)
treed2eeb25d351f25b468184ddfa54931bc498f8713 /fs/adfs
parent6dcc98fbc46511f7a6650946f198df6951a5a88c (diff)
downloadlinux-stable-2220eaf90992c11d888fe771055d4de330385f01.tar.gz
linux-stable-2220eaf90992c11d888fe771055d4de330385f01.tar.bz2
linux-stable-2220eaf90992c11d888fe771055d4de330385f01.zip
ext4: add bounds checking in get_max_inline_xattr_value_size()
Normally the extended attributes in the inode body would have been checked when the inode is first opened, but if someone is writing to the block device while the file system is mounted, it's possible for the inode table to get corrupted. Add bounds checking to avoid reading beyond the end of allocated memory if this happens. Reported-by: syzbot+1966db24521e5f6e23f7@syzkaller.appspotmail.com Link: https://syzkaller.appspot.com/bug?extid=1966db24521e5f6e23f7 Cc: stable@kernel.org Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'fs/adfs')
0 files changed, 0 insertions, 0 deletions