From: 성병찬 <tjdqudcks0424@naver.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Jason Wang" <jasowangio@gmail.com>,
"Eugenio Perez" <eperezma@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
security@kernel.org
Subject: Re: [BUG] virtio_ring: VDUSE backend can corrupt split-ring free list
Date: Tue, 06 Oct 2026 18:39:23 +0900 [thread overview]
Message-ID: <2b6ae98573123157c0d5aca458dd4d1@cweb009.nm> (raw)
In-Reply-To: <20261006052105-mutt-send-email-mst@kernel.org>
Yes, the backend causes the driver to corrupt its own virtqueue
free-list accounting.
My concern was that, after privileged VDUSE setup, a delegated
unprivileged backend can trigger this by modifying a published
descriptor. However, my current reproducer demonstrates duplicate
descriptor allocation only. It does not demonstrate a host
memory-safety violation, cross-device impact, information disclosure,
or privilege escalation.
I therefore agree that the current evidence supports a robustness
issue rather than a confirmed security vulnerability.
Would a patch using the driver-owned desc_extra flags during detach
still be considered worthwhile, or is protection against this backend
behavior outside the intended threat model?
Regards,
sungbyeongchan
next prev parent reply other threads:[~2026-10-06 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 9:12 [BUG] virtio_ring: VDUSE backend can corrupt split-ring free list sungbyeongchan
2026-10-06 9:22 ` Michael S. Tsirkin
2026-10-06 9:39 ` 성병찬 [this message]
2026-10-06 9:48 ` Michael S. Tsirkin
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=2b6ae98573123157c0d5aca458dd4d1@cweb009.nm \
--to=tjdqudcks0424@naver.com \
--cc=eperezma@redhat.com \
--cc=jasowangio@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=security@kernel.org \
--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 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.