mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: cve@kernel.org, linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"security@xenproject.org" <security@xenproject.org>
Subject: Re: CVE-2021-47575: xen/console: harden hvc_xen against event channel storms
Date: Thu, 20 Jun 2024 09:55:06 +0200	[thread overview]
Message-ID: <e7b8ecd4-400e-4af9-bb73-339aa57c3b59@suse.com> (raw)
In-Reply-To: <2024061914-CVE-2021-47575-a011@gregkh>


[-- Attachment #1.1.1: Type: text/plain, Size: 990 bytes --]

On 19.06.24 16:54, Greg Kroah-Hartman wrote:
> Description
> ===========
> 
> In the Linux kernel, the following vulnerability has been resolved:
> 
> xen/console: harden hvc_xen against event channel storms
> 
> The Xen console driver is still vulnerable for an attack via excessive
> number of events sent by the backend. Fix that by using a lateeoi event
> channel.
> 
> For the normal domU initial console this requires the introduction of
> bind_evtchn_to_irq_lateeoi() as there is no xenbus device available
> at the time the event channel is bound to the irq.
> 
> As the decision whether an interrupt was spurious or not requires to
> test for bytes having been read from the backend, move sending the
> event into the if statement, as sending an event without having found
> any bytes to be read is making no sense at all.
> 
> This is part of XSA-391

When issuing XSA-391 the Xen security team already assigned CVE-2021-28713
to this issue.


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

           reply	other threads:[~2024-06-20  7:55 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <2024061914-CVE-2021-47575-a011@gregkh>]

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=e7b8ecd4-400e-4af9-bb73-339aa57c3b59@suse.com \
    --to=jgross@suse.com \
    --cc=cve@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=security@xenproject.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 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®