From: Juergen Gross <jgross@suse.com>
To: cve@kernel.org, linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: CVE-2022-48900: xen/netfront: react properly to failing gnttab_end_foreign_access_ref()
Date: Thu, 22 Aug 2024 07:46:10 +0200 [thread overview]
Message-ID: <608fefca-79e1-4982-9d77-56a56890dd90@suse.com> (raw)
In-Reply-To: <2024082210-CVE-2022-48900-c15e@gregkh>
[-- Attachment #1.1.1: Type: text/plain, Size: 934 bytes --]
Please revoke this CVE, as CVE-2022-23042 has been allocated for this issue
2 years ago already.
This is even clearly visible ...
On 22.08.24 05:31, Greg Kroah-Hartman wrote:
> Description
> ===========
>
> In the Linux kernel, the following vulnerability has been resolved:
>
> xen/netfront: react properly to failing gnttab_end_foreign_access_ref()
>
> When calling gnttab_end_foreign_access_ref() the returned value must
> be tested and the reaction to that value should be appropriate.
>
> In case of failure in xennet_get_responses() the reaction should not be
> to crash the system, but to disable the network device.
>
> The calls in setup_netfront() can be replaced by calls of
> gnttab_end_foreign_access(). While at it avoid double free of ring
> pages and grant references via xennet_disconnect_backend() in this case.
>
> This is CVE-2022-23042 / part of XSA-396.
... here.
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 --]
next parent reply other threads:[~2024-08-22 5:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024082210-CVE-2022-48900-c15e@gregkh>
2024-08-22 5:46 ` Juergen Gross [this message]
2024-08-22 7:31 ` CVE-2022-48900: xen/netfront: react properly to failing gnttab_end_foreign_access_ref() Greg Kroah-Hartman
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=608fefca-79e1-4982-9d77-56a56890dd90@suse.com \
--to=jgross@suse.com \
--cc=cve@kernel.org \
--cc=gregkh@linuxfoundation.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