From: syzbot <syzbot+b2be9dd8ca6f6c73ee2d@syzkaller.appspotmail.com>
To: Pavel Skripkin <paskripkin@gmail.com>
Cc: antony.antony@secunet.com, christian.langrock@secunet.com,
davem@davemloft.net, herbert@gondor.apana.org.au,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, paskripkin@gmail.com,
steffen.klassert@secunet.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] UBSAN: shift-out-of-bounds in xfrm_get_default
Date: Wed, 01 Sep 2021 11:56:21 -0700 [thread overview]
Message-ID: <0000000000004b552c05caf39fd8@google.com> (raw)
In-Reply-To: <52d33ff4-5ddc-0103-9312-f75b7e7cb5b6@gmail.com>
> On 8/30/21 23:19, syzbot wrote:
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: eaf2aaec0be4 Merge tag 'wireless-drivers-next-2021-08-29' ..
>> git tree: net-next
>> console output: https://syzkaller.appspot.com/x/log.txt?x=1219326d300000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=d2f9d4c9ff8c5ae7
>> dashboard link: https://syzkaller.appspot.com/bug?extid=b2be9dd8ca6f6c73ee2d
>> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1
>> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11e6e3a9300000
>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10de8a6d300000
>>
>> The issue was bisected to:
>>
>> commit 2d151d39073aff498358543801fca0f670fea981
>> Author: Steffen Klassert <steffen.klassert@secunet.com>
>> Date: Sun Jul 18 07:11:06 2021 +0000
>>
>> xfrm: Add possibility to set the default to block if we have no policy
>>
>> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=114523fe300000
>> final oops: https://syzkaller.appspot.com/x/report.txt?x=134523fe300000
>> console output: https://syzkaller.appspot.com/x/log.txt?x=154523fe300000
>>
>> IMPORTANT: if you fix the issue, please add the following tag to the commit:
>> Reported-by: syzbot+b2be9dd8ca6f6c73ee2d@syzkaller.appspotmail.com
>> Fixes: 2d151d39073a ("xfrm: Add possibility to set the default to block if we have no policy")
>>
>> netlink: 172 bytes leftover after parsing attributes in process `syz-executor354'.
>> ================================================================================
>> UBSAN: shift-out-of-bounds in net/xfrm/xfrm_user.c:2010:49
>> shift exponent 224 is too large for 32-bit type 'int'
>
>
> #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git
want 2 args (repo, branch), got 3
>
>
>
>
> With regards,
> Pavel Skripkin
next prev parent reply other threads:[~2021-09-01 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 20:19 [syzbot] UBSAN: shift-out-of-bounds in xfrm_get_default syzbot
2021-09-01 18:56 ` Pavel Skripkin
2021-09-01 18:56 ` syzbot [this message]
2021-09-01 18:57 ` Pavel Skripkin
2021-09-01 20:15 ` syzbot
2021-09-01 20:21 ` Pavel Skripkin
2021-09-02 2:15 ` syzbot
2021-09-01 18:56 ` 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=0000000000004b552c05caf39fd8@google.com \
--to=syzbot+b2be9dd8ca6f6c73ee2d@syzkaller.appspotmail.com \
--cc=antony.antony@secunet.com \
--cc=christian.langrock@secunet.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paskripkin@gmail.com \
--cc=steffen.klassert@secunet.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;
as well as URLs for NNTP newsgroup(s).