public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>, linux-erofs@lists.ozlabs.org
Cc: LKML <linux-kernel@vger.kernel.org>,
	syzbot+2ae90e873e97f1faf6f2@syzkaller.appspotmail.com
Subject: Re: [PATCH 2/2] erofs: validate the extent length for uncompressed pclusters
Date: Tue, 6 Dec 2022 23:09:15 +0800	[thread overview]
Message-ID: <3f0b9ff1-eea5-150c-c57e-4e1d0a06e220@kernel.org> (raw)
In-Reply-To: <20221205150050.47784-2-hsiangkao@linux.alibaba.com>

On 2022/12/5 23:00, Gao Xiang wrote:
> syzkaller reported a KASAN use-after-free:
> https://syzkaller.appspot.com/bug?extid=2ae90e873e97f1faf6f2
> 
> The referenced fuzzed image actually has two issues:
>   - m_pa == 0 as a non-inlined pcluster;
>   - The logical length is longer than its physical length.
> 
> The first issue has already been addressed.  This patch addresses
> the second issue by checking the extent length validity.
> 
> Reported-by: syzbot+2ae90e873e97f1faf6f2@syzkaller.appspotmail.com
> Fixes: 02827e1796b3 ("staging: erofs: add erofs_map_blocks_iter")
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,

  reply	other threads:[~2022-12-06 15:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-05 15:00 [PATCH 1/2] erofs: fix missing unmap if z_erofs_get_extent_compressedlen() fails Gao Xiang
2022-12-05 15:00 ` [PATCH 2/2] erofs: validate the extent length for uncompressed pclusters Gao Xiang
2022-12-06 15:09   ` Chao Yu [this message]
2022-12-06  6:22 ` [PATCH 1/2] erofs: fix missing unmap if z_erofs_get_extent_compressedlen() fails Yue Hu
2022-12-06 15:07 ` Chao Yu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3f0b9ff1-eea5-150c-c57e-4e1d0a06e220@kernel.org \
    --to=chao@kernel.org \
    --cc=hsiangkao@linux.alibaba.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+2ae90e873e97f1faf6f2@syzkaller.appspotmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox