From: Alex Williamson <alex.williamson@redhat.com>
To: Like Xu <like.xu.linux@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: eventfd: fix NULL deref irqbypass producer
Date: Tue, 1 Aug 2023 14:26:42 -0600 [thread overview]
Message-ID: <20230801142642.1f73ca45.alex.williamson@redhat.com> (raw)
In-Reply-To: <20230801085408.69597-1-likexu@tencent.com>
On Tue, 1 Aug 2023 16:54:08 +0800
Like Xu <like.xu.linux@gmail.com> wrote:
> From: Like Xu <likexu@tencent.com>
>
> Adding guard logic to make irq_bypass_register/unregister_producer()
> looks for the producer entry based on producer pointer itself instead
> of pure token matching.
>
> As was attempted commit 4f3dbdf47e15 ("KVM: eventfd: fix NULL deref
> irqbypass consumer"), two different producers may occasionally have two
> identical eventfd's. In this case, the later producer may unregister
> the previous one after the registration fails (since they share the same
> token), then NULL deref incurres in the path of deleting producer from
> the producers list.
>
> Registration should also fail if a registered producer changes its
> token and registers again via the same producer pointer.
>
> Cc: Alex Williamson <alex.williamson@redhat.com>
> Signed-off-by: Like Xu <likexu@tencent.com>
> ---
> virt/lib/irqbypass.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Alex Williamson <alex.williamson@redhat.com>
>
> diff --git a/virt/lib/irqbypass.c b/virt/lib/irqbypass.c
> index 28fda42e471b..e0aabbbf27ec 100644
> --- a/virt/lib/irqbypass.c
> +++ b/virt/lib/irqbypass.c
> @@ -98,7 +98,7 @@ int irq_bypass_register_producer(struct irq_bypass_producer *producer)
> mutex_lock(&lock);
>
> list_for_each_entry(tmp, &producers, node) {
> - if (tmp->token == producer->token) {
> + if (tmp->token == producer->token || tmp == producer) {
> ret = -EBUSY;
> goto out_err;
> }
> @@ -148,7 +148,7 @@ void irq_bypass_unregister_producer(struct irq_bypass_producer *producer)
> mutex_lock(&lock);
>
> list_for_each_entry(tmp, &producers, node) {
> - if (tmp->token != producer->token)
> + if (tmp != producer)
> continue;
>
> list_for_each_entry(consumer, &consumers, node) {
>
> base-commit: 5a7591176c47cce363c1eed704241e5d1c42c5a6
prev parent reply other threads:[~2023-08-01 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 8:54 Like Xu
2023-08-01 20:26 ` Alex Williamson [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=20230801142642.1f73ca45.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=like.xu.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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®