From: syzbot <syzbot+a25ee9d20d31e483ba7b@syzkaller.appspotmail.com>
To: davem@davemloft.net, eadavis@qq.com, edumazet@google.com,
hdanton@sina.com, herbert@gondor.apana.org.au, horms@kernel.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
saakashkumar@marvell.com, sd@queasysnail.net,
steffen.klassert@secunet.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] KASAN: slab-use-after-free Write in __xfrm_state_delete
Date: Thu, 28 Aug 2025 00:25:05 -0700 [thread overview]
Message-ID: <68b00451.a00a0220.1337b0.0003.GAE@google.com> (raw)
In-Reply-To: <68887370.a00a0220.b12ec.00cb.GAE@google.com>
syzbot has bisected this issue to:
commit 94f39804d891cffe4ce17737d295f3b195bc7299
Author: Aakash Kumar S <saakashkumar@marvell.com>
Date: Mon Jun 30 12:38:56 2025 +0000
xfrm: Duplicate SPI Handling
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17d07c42580000
start commit: b1c92cdf5af3 Merge branch 'net-wangxun-complete-ethtool-co..
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=14307c42580000
console output: https://syzkaller.appspot.com/x/log.txt?x=10307c42580000
kernel config: https://syzkaller.appspot.com/x/.config?x=67b99ceb67d33475
dashboard link: https://syzkaller.appspot.com/bug?extid=a25ee9d20d31e483ba7b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14221862580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=159fba34580000
Reported-by: syzbot+a25ee9d20d31e483ba7b@syzkaller.appspotmail.com
Fixes: 94f39804d891 ("xfrm: Duplicate SPI Handling")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-08-28 7:25 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 7:08 [syzbot] [net?] KASAN: slab-use-after-free Write in __xfrm_state_delete syzbot
2025-08-24 19:21 ` syzbot
2025-08-25 1:10 ` Hillf Danton
2025-08-25 1:51 ` syzbot
2025-08-25 4:51 ` Hillf Danton
2025-08-25 12:33 ` syzbot
2025-08-25 12:44 ` Hillf Danton
2025-08-25 14:13 ` syzbot
2025-08-25 15:59 ` Sabrina Dubroca
2025-08-26 3:27 ` Hillf Danton
2025-08-26 3:53 ` syzbot
2025-08-26 4:16 ` Hillf Danton
2025-08-26 5:12 ` syzbot
2025-08-26 7:31 ` Hillf Danton
2025-08-26 11:11 ` syzbot
2025-08-26 9:41 ` Edward Adam Davis
2025-08-26 11:34 ` syzbot
2025-08-26 13:22 ` Hillf Danton
2025-08-26 19:54 ` syzbot
2025-08-27 0:40 ` Hillf Danton
2025-08-27 2:44 ` syzbot
2025-08-27 1:30 ` Edward Adam Davis
2025-08-27 3:03 ` syzbot
2025-08-27 4:51 ` Hillf Danton
2025-08-27 6:27 ` syzbot
2025-08-27 5:18 ` Hillf Danton
2025-08-27 6:44 ` syzbot
2025-08-27 5:49 ` Edward Adam Davis
2025-08-27 6:44 ` syzbot
2025-08-27 6:56 ` Edward Adam Davis
2025-08-27 7:26 ` syzbot
2025-08-27 7:57 ` Hillf Danton
2025-08-27 8:22 ` syzbot
2025-08-27 8:10 ` Edward Adam Davis
2025-08-27 9:14 ` syzbot
2025-08-27 8:39 ` Hillf Danton
2025-08-27 9:31 ` syzbot
2025-08-27 9:35 ` Edward Adam Davis
2025-08-27 10:23 ` syzbot
2025-08-27 10:07 ` Hillf Danton
2025-08-27 10:41 ` syzbot
2025-08-27 11:00 ` Hillf Danton
2025-08-27 11:48 ` syzbot
2025-08-28 7:25 ` 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=68b00451.a00a0220.1337b0.0003.GAE@google.com \
--to=syzbot+a25ee9d20d31e483ba7b@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=eadavis@qq.com \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saakashkumar@marvell.com \
--cc=sd@queasysnail.net \
--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).