public inbox for linux-kernel@vger.kernel.org
 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-47574: xen/netfront: harden netfront against event channel storms
Date: Thu, 20 Jun 2024 09:54:11 +0200	[thread overview]
Message-ID: <87d1ece9-246f-4e53-bb7d-4cd965d56dbd@suse.com> (raw)
In-Reply-To: <2024061914-CVE-2021-47574-18b4@gregkh>


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

On 19.06.24 16:54, Greg Kroah-Hartman wrote:
> Description
> ===========
> 
> In the Linux kernel, the following vulnerability has been resolved:
> 
> xen/netfront: harden netfront against event channel storms
> 
> The Xen netfront driver is still vulnerable for an attack via excessive
> number of events sent by the backend. Fix that by using lateeoi event
> channels.
> 
> For being able to detect the case of no rx responses being added while
> the carrier is down a new lock is needed in order to update and test
> rsp_cons and the number of seen unconsumed responses atomically.
> 
> This is part of XSA-391

When issuing XSA-391 the Xen security team already assigned CVE-2021-28712
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:54 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <2024061914-CVE-2021-47574-18b4@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=87d1ece9-246f-4e53-bb7d-4cd965d56dbd@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