From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: syzbot <syzbot+2ff22910687ee0dfd48e@syzkaller.appspotmail.com>
Cc: dakr@kernel.org, djrscally@gmail.com, gregkh@linuxfoundation.org,
heikki.krogerus@linux.intel.com, jgg@nvidia.com,
kevin.tian@intel.com, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, nicolinc@nvidia.com,
rafael@kernel.org, sakari.ailus@linux.intel.com,
syzkaller-bugs@googlegroups.com, yi.l.liu@intel.com
Subject: Re: [syzbot] [acpi?] KASAN: slab-use-after-free Read in software_node_notify_remove
Date: Sun, 6 Apr 2025 16:24:41 +0300 [thread overview]
Message-ID: <Z_KAmSNLsAhctKv8@smile.fi.intel.com> (raw)
In-Reply-To: <67f26778.050a0220.0a13.0265.GAE@google.com>
On Sun, Apr 06, 2025 at 04:37:28AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: acc4d5ff0b61 Merge tag 'net-6.15-rc0' of git://git.kernel...
> git tree: upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=15a807cf980000
> kernel config: https://syzkaller.appspot.com/x/.config?x=24f9c4330e7c0609
> dashboard link: https://syzkaller.appspot.com/bug?extid=2ff22910687ee0dfd48e
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=109077b0580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13717c3f980000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/e4bfa652b34a/disk-acc4d5ff.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/3d19beb8bb92/vmlinux-acc4d5ff.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/e7298ccc6331/bzImage-acc4d5ff.xz
#syz test: https://bitbucket.org/andy-shev/linux.git test-swnode
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-04-06 13:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-06 11:37 [syzbot] [acpi?] KASAN: slab-use-after-free Read in software_node_notify_remove syzbot
2025-04-06 13:13 ` Andy Shevchenko
2025-04-06 13:31 ` syzbot
2025-04-06 13:24 ` Andy Shevchenko [this message]
2025-04-06 14:09 ` syzbot
2025-04-08 14:54 ` Andy Shevchenko
2025-04-10 0:57 ` [syzbot] " syzbot
2025-04-10 14:23 ` syzbot
2025-04-11 0:42 ` [PATCH] software node: Prevent link creation failure from causing kobj reference count imbalance Lizhi Xu
2025-04-14 6:20 ` Andy Shevchenko
2025-04-14 6:27 ` Andy Shevchenko
2025-04-14 7:08 ` Lizhi Xu
2025-04-14 7:16 ` Andy Shevchenko
2025-04-14 7:11 ` [PATCH V2] " Lizhi Xu
2025-04-14 7:22 ` Andy Shevchenko
2025-04-14 8:41 ` Sakari Ailus
[not found] <20250410005712.2532007-1-lizhi.xu@windriver.com>
2025-04-10 4:43 ` [syzbot] [acpi?] KASAN: slab-use-after-free Read in software_node_notify_remove syzbot
[not found] <20250410111546.3939-1-hdanton@sina.com>
2025-04-10 11:58 ` syzbot
[not found] <20250410142307.164379-1-lizhi.xu@windriver.com>
2025-04-10 19:11 ` syzbot
[not found] <20250415110145.4052-1-hdanton@sina.com>
2025-04-15 11:35 ` 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=Z_KAmSNLsAhctKv8@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dakr@kernel.org \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=syzbot+2ff22910687ee0dfd48e@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yi.l.liu@intel.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.