From: syzbot <syzbot+27d7cfbc93457e472e00@syzkaller.appspotmail.com>
To: atenart@kernel.org, davem@davemloft.net,
dawid.osuchowski@linux.intel.com, edumazet@google.com,
gal@nvidia.com, horms@kernel.org, kuba@kernel.org,
kuniyu@google.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] KASAN: null-ptr-deref Write in rcuref_put (4)
Date: Tue, 05 Aug 2025 04:34:02 -0700 [thread overview]
Message-ID: <6891ec2a.050a0220.7f033.0021.GAE@google.com> (raw)
In-Reply-To: <67f66c9c.050a0220.25d1c8.0003.GAE@google.com>
syzbot has bisected this issue to:
commit de9c4861fb42f0cd72da844c3c34f692d5895b7b
Author: Eric Dumazet <edumazet@google.com>
Date: Tue Jul 29 08:02:07 2025 +0000
pptp: ensure minimal skb length in pptp_xmit()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17cb2042580000
start commit: 5c5a10f0be96 Add linux-next specific files for 20250804
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=142b2042580000
console output: https://syzkaller.appspot.com/x/log.txt?x=102b2042580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f4ccbd076877954b
dashboard link: https://syzkaller.appspot.com/bug?extid=27d7cfbc93457e472e00
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1628faa2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12490434580000
Reported-by: syzbot+27d7cfbc93457e472e00@syzkaller.appspotmail.com
Fixes: de9c4861fb42 ("pptp: ensure minimal skb length in pptp_xmit()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-08-05 11:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 12:48 [syzbot] [net?] KASAN: null-ptr-deref Write in rcuref_put (4) syzbot
2025-08-04 11:12 ` syzbot
2025-08-04 13:08 ` Eric Dumazet
2025-08-04 17:12 ` syzbot
2025-08-05 11:34 ` syzbot [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=6891ec2a.050a0220.7f033.0021.GAE@google.com \
--to=syzbot+27d7cfbc93457e472e00@syzkaller.appspotmail.com \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=dawid.osuchowski@linux.intel.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.