From: Thorsten Blum <blum@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Laurent Vivier <lvivier@redhat.com>,
Olivia Mackall <olivia@selenic.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Amos Kong <akong@redhat.com>,
virtualization@lists.linux.dev, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwrng: virtio - prevent use-after-free after a failed restore
Date: Fri, 6 Nov 2026 12:30:23 +0100 [thread overview]
Message-ID: <au26T4dmLXWFkxPv@kernel.org> (raw)
In-Reply-To: <au219vQfcYE0maYw@gondor.apana.org.au>
Hi Herbert,
On Fri, Nov 06, 2026 at 07:11:50PM +0800, Herbert Xu wrote:
> On Fri, Oct 16, 2026 at 12:36:40PM +0200, Thorsten Blum wrote:
> > remove_common() frees the driver data during freeze, but does not clear
> > vdev->priv, which points to freed memory. If probe_common() then fails
> > during restore, a later remove or freeze can dereference the dangling
> > pointer.
> >
> > Clear vdev->priv on the probe_common() error cleanup path and before
> > freeing the driver data in remove_common(). Also reset the device and
> > return early from remove_common() if vdev->priv is already NULL for a
> > safe teardown after a failed restore.
> >
> > Fixes: 08e53fbdb85c ("virtio-rng: support multiple virtio-rng devices")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Thorsten Blum <blum@kernel.org>
> > ---
> > drivers/char/hw_random/virtio-rng.c | 7 +++++++
> > 1 file changed, 7 insertions(+)
>
> Please respond to this comment:
>
> https://sashiko.dev/#/patchset/20261016103640.4989-2-blum%40kernel.org
I think the issue raised by Sashiko is valid, but also pre-existing and
could therefore be fixed in a separate follow-up patch.
Thanks,
Thorsten
next prev parent reply other threads:[~2026-11-06 11:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 10:36 [PATCH] hwrng: virtio - prevent use-after-free after a failed restore Thorsten Blum
2026-10-16 10:47 ` sashiko-bot
2026-10-18 17:00 ` PrasannaKumar Muralidharan
2026-10-18 20:37 ` Thorsten Blum
2026-10-19 13:00 ` PrasannaKumar Muralidharan
2026-11-06 11:11 ` Herbert Xu
2026-11-06 11:30 ` Thorsten Blum [this message]
2026-11-11 11:12 ` Herbert Xu
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=au26T4dmLXWFkxPv@kernel.org \
--to=blum@kernel.org \
--cc=akong@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvivier@redhat.com \
--cc=olivia@selenic.com \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux.dev \
/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.