From: Linus Torvalds <torvalds@linux-foundation.org>
To: syzbot <syzbot+48135e34de22e3a82c99@syzkaller.appspotmail.com>
Cc: applications@thinkbigglobal.in,
David Miller <davem@davemloft.net>,
gustavo@padovan.org, Johan Hedberg <johan.hedberg@gmail.com>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
Ingo Molnar <mingo@redhat.com>, Michal Marek <mmarek@suse.com>,
Netdev <netdev@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Will Deacon <will@kernel.org>
Subject: Re: [syzbot] KASAN: use-after-free Read in corrupted (4)
Date: Sun, 22 May 2022 20:56:18 -0700 [thread overview]
Message-ID: <CAHk-=whH5pmgyzE6+6C==p2VQFUgGiPhSwX=R2zKs+iHZuX7_A@mail.gmail.com> (raw)
In-Reply-To: <000000000000b6b4eb05dfa1b325@google.com>
On Sun, May 22, 2022 at 4:01 PM syzbot
<syzbot+48135e34de22e3a82c99@syzkaller.appspotmail.com> wrote:
>
> The issue was bisected to:
>
> commit c470abd4fde40ea6a0846a2beab642a578c0b8cd
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Sun Feb 19 22:34:00 2017 +0000
>
> Linux 4.10
Heh. That looks very unlikely, so the bisection seems to sadly have
failed at some point.
At least one of the KASAN reports (that "final oops") does look very
much like the bug fixed by commit 1bff51ea59a9 ("Bluetooth: fix
use-after-free error in lock_sock_nested()"), so this may already be
fixed, but who knows...
But that "update Makefile to 4.10" is not the cause...
Linus
next prev parent reply other threads:[~2022-05-23 4:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 12:47 KASAN: use-after-free Read in corrupted (4) syzbot
2022-05-22 23:01 ` [syzbot] " syzbot
2022-05-23 3:56 ` Linus Torvalds [this message]
2022-06-01 13:51 ` Aleksandr Nogikh
[not found] <20220523000922.2997-1-hdanton@sina.com>
2022-05-23 0:27 ` syzbot
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='CAHk-=whH5pmgyzE6+6C==p2VQFUgGiPhSwX=R2zKs+iHZuX7_A@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=applications@thinkbigglobal.in \
--cc=davem@davemloft.net \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mingo@redhat.com \
--cc=mmarek@suse.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=syzbot+48135e34de22e3a82c99@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=will@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).