From: Sabyrzhan Tasbolatov <snovitoll@gmail.com>
To: syzbot <syzbot+61123a5daeb9f7454599@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] KASAN: out-of-bounds Read in copy_from_kernel_nofault
Date: Mon, 30 Sep 2024 18:53:52 +0500 [thread overview]
Message-ID: <CACzwLxj+Tbnn5Cwbezr+7VVrrsQD5Cev=o4+EkEFkp2v_QPFAQ@mail.gmail.com> (raw)
In-Reply-To: <66faaa4e.050a0220.aab67.0032.GAE@google.com>
On Mon, Sep 30, 2024 at 6:40 PM syzbot
<syzbot+61123a5daeb9f7454599@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: cea5425829f7 Add linux-next specific files for 20240930
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=14eccea9980000
> kernel config: https://syzkaller.appspot.com/x/.config?x=41a28720ed564c6a
> dashboard link: https://syzkaller.appspot.com/bug?extid=61123a5daeb9f7454599
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/566995596f19/disk-cea54258.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/e7c506c1c71d/vmlinux-cea54258.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/7fcb4468b8c0/bzImage-cea54258.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+61123a5daeb9f7454599@syzkaller.appspotmail.com
>
> ==================================================================
> BUG: KASAN: out-of-bounds in instrument_memcpy_before include/linux/instrumented.h:163 [inline]
> BUG: KASAN: out-of-bounds in copy_from_kernel_nofault+0x7a/0x2f0 mm/maccess.c:35
> Read of size 6 at addr fffffffffffffffd by task syz.1.54/5558
This is due to the recent commit in mm/maccess.c and
might be false-positive according to the report.
Fix for the proper arguments' check has been already sent.
See pending patch:
https://lore.kernel.org/linux-mm/20240930102405.2227124-1-snovitoll@gmail.com/T/#u
next prev parent reply other threads:[~2024-09-30 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 13:40 syzbot
2024-09-30 13:53 ` Sabyrzhan Tasbolatov [this message]
2024-10-01 4:22 ` syzbot
2024-10-01 23:25 ` 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='CACzwLxj+Tbnn5Cwbezr+7VVrrsQD5Cev=o4+EkEFkp2v_QPFAQ@mail.gmail.com' \
--to=snovitoll@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+61123a5daeb9f7454599@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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