From: Paolo Abeni <pabeni@redhat.com>
To: Jason Wang <jasowang@redhat.com>,
syzbot <syzbot+ac856b8b866cca41352c@syzkaller.appspotmail.com>
Cc: eperezma@redhat.com, linux-kernel@vger.kernel.org,
mst@redhat.com, syzkaller-bugs@googlegroups.com,
virtualization@lists.linux.dev, xuanzhuo@linux.alibaba.com
Subject: Re: [syzbot] [virt?] upstream test error: KMSAN: use-after-free in vring_map_one_sg
Date: Mon, 13 Oct 2025 09:37:29 +0200 [thread overview]
Message-ID: <0f20cd6a-d9aa-4837-a120-1e2e7dbdc954@redhat.com> (raw)
In-Reply-To: <CACGkMEsh_j9wCAv-LwOVxLjvUzEuKuu+7ZGMGcdJr7ettdBYTQ@mail.gmail.com>
On 10/13/25 9:20 AM, Jason Wang wrote:
> On Mon, Oct 13, 2025 at 1:29 PM Jason Wang <jasowang@redhat.com> wrote:
>> On Sat, Oct 11, 2025 at 3:40 PM Jason Wang <jasowang@redhat.com> wrote:
>>>
>>> #syz test
>>>
>>> On Sat, Oct 11, 2025 at 4:38 AM syzbot
>>> <syzbot+ac856b8b866cca41352c@syzkaller.appspotmail.com> wrote:
>>
>> Paolo, it looks like the GSO tunnel features will leave uninitialized
>> vnet header field which trigger KMSAN warning.
>>
>> Please have a look at the patch (which has been tested by syzbot) or
>> propose another one.
>
> Forget the attachment.
I have a few questions. The report mentions both UaF and uninit; the
patch addresses "just" the uninit access. It's not clear to me if and
how the UaF is addressed, and why/if it's related to the uninit access.
Do you know better?
It looks like the uninit root cause is on "the other side"? i.e. the
device not initializing properly the header. Would unconditionally
clearing the hash info implicitly disable such feature?
The syzbot dashboard mentions a (no more available) reproducer. Do you
have it cached somewhere?
Thanks,
Paolo
next prev parent reply other threads:[~2025-10-13 7:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 20:38 syzbot
2025-10-11 6:10 ` Forwarded: " syzbot
2025-10-11 7:40 ` Jason Wang
2025-10-11 9:20 ` syzbot
2025-10-13 5:29 ` Jason Wang
2025-10-13 7:20 ` Jason Wang
2025-10-13 7:37 ` Paolo Abeni [this message]
2025-10-13 8:08 ` Michael S. Tsirkin
2025-10-13 8:17 ` Paolo Abeni
2025-10-14 2:41 ` Jason Wang
2025-10-14 6:47 ` Paolo Abeni
2025-10-14 2:38 ` Jason Wang
[not found] <CACGkMEvXKYK2tWs=XuM9L=SzZfPwuiKPpd1CpBQq9APJUthRuw@mail.gmail.com>
2025-10-11 6:52 ` 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=0f20cd6a-d9aa-4837-a120-1e2e7dbdc954@redhat.com \
--to=pabeni@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=syzbot+ac856b8b866cca41352c@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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
all inboxes | Powered by JetHome®