From: Greg KH <gregkh@linuxfoundation.org>
To: Joseph Bursey <jbursey@uci.edu>
Cc: syzbot <syzbot+ad2aac2febc3bedf0962@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] KASAN: slab-use-after-free Write in iowarrior_write_callback (2)
Date: Sat, 23 May 2026 06:19:39 +0200 [thread overview]
Message-ID: <2026052320-deem-egging-4b84@gregkh> (raw)
In-Reply-To: <32c79569-8001-48d2-9675-b38b1670f285@uci.edu>
On Fri, May 22, 2026 at 01:38:40PM -0700, Joseph Bursey wrote:
> Hello, I believe I have a reproducer for this bug using a combination
> of syz-execprog and eBPF programs. There are three artifacts used to
> reproduce the bug: prog.syz loader.c and func.bpf.c, which can be
> compiled as follows:
>
> bpftool btf dump file linux/vmlinux format c > vmlinux.h
> gcc loader.c -o loader -lbpf -lelf -lz -static -lzstd
> clang -O2 -g -target bpf -c func.bpf.c -o func.bpf.o
>
> And then run using syz-execprog:
>
> ./loader & ./syz-execprog -executor=./syz-executor -enable=usb,close_fds
> -repeat=0 -procs=4 -threaded -collide -slowdown=1 ./prog.syz
>
> The following configs were added to what Syzkaller used:
> CONFIG_KPROBES=y
> CONFIG_KPROBE_EVENTS=y
> CONFIG_FTRACE_SYSCALLS=y
> CONFIG_DEBUG_INFO_BTF=y
> CONFIG_DEBUG_INFO_BTF_MODULES=y
> CONFIG_FUNCTION_TRACER=y
> CONFIG_KPROBE_EVENTS_ON_NOTRACE=y
>
> I am interested to know if eBPF based reproducers are helpful during
> the debugging process.
If you can use that to create a fix, great! Otherwise there's not much
we can do here with this :)
thanks,
greg k-h
next prev parent reply other threads:[~2026-05-23 4:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 22:26 [syzbot] [usb?] KASAN: slab-use-after-free Write in iowarrior_write_callback (2) syzbot
2026-05-22 20:38 ` Joseph Bursey
2026-05-23 4:19 ` Greg KH [this message]
2026-05-24 8:30 ` Michal Pecio
2026-05-24 14:45 ` Alan Stern
2026-05-24 16:46 ` Michal Pecio
[not found] ` <CACR97nvAMAnfEL+j5GCi9zcmNc9VLtbAtO0ywEtbBdrw=YSHhQ@mail.gmail.com>
2026-05-28 8:20 ` Michal Pecio
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=2026052320-deem-egging-4b84@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jbursey@uci.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=syzbot+ad2aac2febc3bedf0962@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 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.