From: Sean Christopherson <seanjc@google.com>
To: Hillf Danton <hdanton@sina.com>
Cc: syzbot <syzbot+2479e53d0db9b32ae2aa@syzkaller.appspotmail.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tabba@google.com,
xiaoyao.li@intel.com
Subject: Re: [syzbot] [kvm?] KASAN: slab-use-after-free Write in kvm_gmem_release
Date: Mon, 27 Oct 2025 07:41:47 -0700 [thread overview]
Message-ID: <aP-Eq4NFAhIscvIf@google.com> (raw)
In-Reply-To: <20251025015852.8771-1-hdanton@sina.com>
On Sat, Oct 25, 2025, Hillf Danton wrote:
> On Thu, Oct 23, 2025, syzbot wrote:
> > syzbot has bisected this issue to:
> >
> > commit d1e54dd08f163a9021433020d16a8f8f70ddc41c
> > Author: Fuad Tabba <tabba@google.com>
> > Date: Tue Jul 29 22:54:40 2025 +0000
> >
> > KVM: x86: Enable KVM_GUEST_MEMFD for all 64-bit builds
> >
> > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12a663cd980000
> > start commit: 43e9ad0c55a3 Merge tag 'scsi-fixes' of git://git.kernel.or..
> > git tree: upstream
> > final oops: https://syzkaller.appspot.com/x/report.txt?x=11a663cd980000
> > console output: https://syzkaller.appspot.com/x/log.txt?x=16a663cd980000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=67b63a24f3c26fca
> > dashboard link: https://syzkaller.appspot.com/bug?extid=2479e53d0db9b32ae2aa
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=173ecd2f980000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14bc2be2580000
>
> Test Sean's fix.
>
> #syz test linux-next master
Oh, nice. Thanks Hillf!
prev parent reply other threads:[~2025-10-27 14:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 18:55 [syzbot] [kvm?] KASAN: slab-use-after-free Write in kvm_gmem_release syzbot
2025-10-24 6:15 ` syzbot
2025-10-24 19:14 ` Sean Christopherson
2025-10-24 20:10 ` syzbot
2025-10-24 23:24 ` Hillf Danton
2025-10-24 23:27 ` syzbot
2025-10-24 23:43 ` Hillf Danton
2025-10-25 0:12 ` syzbot
2025-10-25 1:58 ` Hillf Danton
2025-10-25 3:42 ` syzbot
2025-10-27 14:41 ` Sean Christopherson [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=aP-Eq4NFAhIscvIf@google.com \
--to=seanjc@google.com \
--cc=hdanton@sina.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+2479e53d0db9b32ae2aa@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tabba@google.com \
--cc=xiaoyao.li@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox