linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: SyzScope <syzscope@gmail.com>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
	syzbot <syzbot+9b91d635e2b51efd6371@syzkaller.appspotmail.com>,
	Martin Fuzzey <mfuzzey@parkeon.com>,
	Shuah Khan <shuah@kernel.org>,
	linux-kernel@vger.kernel.org, rafael@kernel.org,
	sunjunyong@xiaomi.com, sunjy516@gmail.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Read in fw_load_sysfs_fallback
Date: Wed, 2 Jun 2021 19:56:32 +0200	[thread overview]
Message-ID: <YLfGUNpTU5BE27IT@kroah.com> (raw)
In-Reply-To: <07acfc7a-cfa4-5f14-b2ee-14790ff58363@gmail.com>

On Wed, Jun 02, 2021 at 10:08:39AM -0700, SyzScope wrote:
> Hi,
> We have analyzed this bug and realize that it is security-critical.
> Specifically, according to our investigation, it will lead to a
> use-after-free write (instead of the originally reported use-after-free
> read) and thus highly likely exploitable. More details can be found at:
> 
> https://sites.google.com/view/syzscope/kasan-use-after-free-read-in-fw_load_sysfs_fallback <https://sites.google.com/view/syzscope/kasan-use-after-free-read-in-fw_load_sysfs_fallback>
> 
> 
> We understand that creating a patch can be time-consuming and there is
> probably a long list of bugs pending fixes. We hope that our security
> analysis can enable an informed decision on which bugs to fix first
> (prioritization).
> 
> Since the bug has been on syzbot for over two months (first found on
> 03-22-2020), it is best to have the bug fixed early enough to avoid it being
> weaponized.

Great, please work to provide a fix!  See the archives for more details
if you are curious about this.

thanks,

greg k-h

      reply	other threads:[~2021-06-02 17:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-02 21:41 syzbot
2021-04-03  1:31 ` Luis Chamberlain
2021-06-02 17:08   ` SyzScope
2021-06-02 17:56     ` Greg KH [this message]

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=YLfGUNpTU5BE27IT@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=mfuzzey@parkeon.com \
    --cc=rafael@kernel.org \
    --cc=shuah@kernel.org \
    --cc=sunjunyong@xiaomi.com \
    --cc=sunjy516@gmail.com \
    --cc=syzbot+9b91d635e2b51efd6371@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=syzscope@gmail.com \
    --subject='Re: [syzbot] KASAN: use-after-free Read in fw_load_sysfs_fallback' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).