From: Greg KH <gregkh@linuxfoundation.org>
To: Juergen Gross <jgross@suse.com>
Cc: cve@kernel.org, linux-cve-announce@vger.kernel.org,
linux-kernel@vger.kernel.org,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"Xen.org security team" <security@xen.org>
Subject: Re: CVE-2021-47377: kernel: xen/balloon: use a kernel thread instead a workqueue
Date: Tue, 28 May 2024 21:03:01 +0200 [thread overview]
Message-ID: <2024052826-overpass-manliness-7f2c@gregkh> (raw)
In-Reply-To: <9fba239d-2e22-425b-b45f-86ecf016c2fd@suse.com>
On Mon, May 27, 2024 at 12:58:16PM +0200, Juergen Gross wrote:
> Hi,
>
> I'd like to dispute CVE-2021-47377: the issue fixed by upstream commit
> 8480ed9c2bbd56fc86524998e5f2e3e22f5038f6 can in no way be triggered by
> an unprivileged user or by a remote attack of the system, as it requires
> initiation of memory ballooning of the running system. This can be done
> only by either a host admin or by an admin of the guest which might
> suffer the detection of the hanging workqueue.
>
> Please revoke this CVE.
Ah, good catch, this came in as part of the GSD import, and I missed
that this required that type of permissions. Now revoked, thanks for
the review!
greg k-h
prev parent reply other threads:[~2024-05-28 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024041747-CVE-2024-26908-4690@gregkh>
2024-04-29 11:53 ` CVE-2024-26908: x86/xen: Add some null pointer checking to smp.c Juergen Gross
2024-04-30 8:11 ` Greg KH
2024-05-27 10:58 ` CVE-2021-47377: kernel: xen/balloon: use a kernel thread instead a workqueue Juergen Gross
2024-05-28 19:03 ` Greg KH [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=2024052826-overpass-manliness-7f2c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=jgross@suse.com \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=security@xen.org \
--cc=xen-devel@lists.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