From: syzbot <syzbot+0948c82180d475ad24e2@syzkaller.appspotmail.com>
To: aha310510@gmail.com, bp@alien8.de, dave.hansen@linux.intel.com,
dwmw2@infradead.org, halves@igalia.com, hpa@zytor.com,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, paul@xen.org, pbonzini@redhat.com,
pdurrant@amazon.com, seanjc@google.com,
souradiptodas6@gmail.com, stable@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tglx@kernel.org,
x86@kernel.org
Subject: Re: [syzbot] [kvm?] [kvm-x86?] KASAN: use-after-free Read in kvm_xen_shared_info_init
Date: Wed, 05 Aug 2026 08:46:01 -0700 [thread overview]
Message-ID: <6a735ab9.41e285c5.91630.006b.GAE@google.com> (raw)
In-Reply-To: <05be9bb6c5609ca9fc503c25596c9c9e411591d6.camel@infradead.org>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+0948c82180d475ad24e2@syzkaller.appspotmail.com
Tested-by: syzbot+0948c82180d475ad24e2@syzkaller.appspotmail.com
Tested on:
commit: bd2b92fd [NOT-FOR-UPSTREAM] repro: pfncache HVA-invali..
git tree: git://git.infradead.org/users/dwmw2/linux.git pfncache-fixes
console output: https://syzkaller.appspot.com/x/log.txt?x=10362bb9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=145fa60d73086782
dashboard link: https://syzkaller.appspot.com/bug?extid=0948c82180d475ad24e2
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2026-08-05 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 13:01 [syzbot] [kvm?] [kvm-x86?] KASAN: use-after-free Read in kvm_xen_shared_info_init syzbot
2026-08-02 15:56 ` syzbot
2026-08-05 14:01 ` syzbot
2026-08-05 14:47 ` David Woodhouse
2026-08-05 15:46 ` syzbot [this message]
2026-08-05 16:00 ` David Woodhouse
2026-08-05 16:55 ` 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=6a735ab9.41e285c5.91630.006b.GAE@google.com \
--to=syzbot+0948c82180d475ad24e2@syzkaller.appspotmail.com \
--cc=aha310510@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=halves@igalia.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=pdurrant@amazon.com \
--cc=seanjc@google.com \
--cc=souradiptodas6@gmail.com \
--cc=stable@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@kernel.org \
--cc=x86@kernel.org \
/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.