summaryrefslogtreecommitdiff
path: root/fs/binfmt_aout.c
diff options
context:
space:
mode:
authorBrian Foster <bfoster@redhat.com>2019-12-03 18:53:15 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-01-12 13:22:40 +0300
commit03e47594564a435e6c2890142476b93e82090c2e (patch)
tree9ec4f2dd3485cba0f03b2c82af0f0b08a3544e7e /fs/binfmt_aout.c
parent91f060f5c5c8fe3b8d171e1d191512c400780352 (diff)
downloadlinux-03e47594564a435e6c2890142476b93e82090c2e.tar.xz
xfs: fix mount failure crash on invalid iclog memory access
[ Upstream commit 798a9cada4694ca8d970259f216cec47e675bfd5 ] syzbot (via KASAN) reports a use-after-free in the error path of xlog_alloc_log(). Specifically, the iclog freeing loop doesn't handle the case of a fully initialized ->l_iclog linked list. Instead, it assumes that the list is partially constructed and NULL terminated. This bug manifested because there was no possible error scenario after iclog list setup when the original code was added. Subsequent code and associated error conditions were added some time later, while the original error handling code was never updated. Fix up the error loop to terminate either on a NULL iclog or reaching the end of the list. Reported-by: syzbot+c732f8644185de340492@syzkaller.appspotmail.com Signed-off-by: Brian Foster <bfoster@redhat.com> Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'fs/binfmt_aout.c')
0 files changed, 0 insertions, 0 deletions