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,
	linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: CVE-2021-47581: xen/netback: don't queue unlimited number of packages
Date: Thu, 20 Jun 2024 09:57:20 +0200	[thread overview]
Message-ID: <e0a4a1e7-a626-4bfd-973f-d27474bea142@suse.com> (raw)
In-Reply-To: <2024061916-CVE-2021-47581-1d34@gregkh>


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

On 19.06.24 16:54, Greg Kroah-Hartman wrote:
> Description
> ===========
> 
> In the Linux kernel, the following vulnerability has been resolved:
> 
> xen/netback: don't queue unlimited number of packages
> 
> In case a guest isn't consuming incoming network traffic as fast as it
> is coming in, xen-netback is buffering network packages in unlimited
> numbers today. This can result in host OOM situations.
> 
> Commit f48da8b14d04ca8 ("xen-netback: fix unlimited guest Rx internal
> queue and carrier flapping") meant to introduce a mechanism to limit
> the amount of buffered data by stopping the Tx queue when reaching the
> data limit, but this doesn't work for cases like UDP.
> 
> When hitting the limit don't queue further SKBs, but drop them instead.
> In order to be able to tell Rx packages have been dropped increment the
> rx_dropped statistics counter in this case.
> 
> It should be noted that the old solution to continue queueing SKBs had
> the additional problem of an overflow of the 32-bit rx_queue_len value
> would result in intermittent Tx queue enabling.
> 
> This is part of XSA-392
> 
> The Linux kernel CVE team has assigned CVE-2021-47581 to this issue.

When issuing XSA-392 the Xen security team already assigned CVE-2021-28715
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:57 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <2024061916-CVE-2021-47581-1d34@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=e0a4a1e7-a626-4bfd-973f-d27474bea142@suse.com \
    --to=jgross@suse.com \
    --cc=cve@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-cve-announce@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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®