From: Juergen Gross <jgross@suse.com>
To: gregkh@linuxfoundation.org
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-2024-26908: x86/xen: Add some null pointer checking to smp.c
Date: Mon, 29 Apr 2024 13:53:44 +0200 [thread overview]
Message-ID: <f73bb0fe-9ba6-46de-8732-bd372438068e@suse.com> (raw)
In-Reply-To: <2024041747-CVE-2024-26908-4690@gregkh>
[-- Attachment #1.1.1: Type: text/plain, Size: 438 bytes --]
Hi,
I'd like to dispute CVE-2024-26908: the issue fixed by upstream commit
3693bb4465e6e32a204a5b86d3ec7e6b9f7e67c2 can in no way be triggered by
an unprivileged user or by a remote attack of the system, as it requires
hotplug of (virtual) cpus to the running system. This can be done only by
either a host admin or by an admin of the guest which might suffer the
out-of-memory situation.
Please revoke this CVE.
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-04-29 11:54 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 ` Juergen Gross [this message]
2024-04-30 8:11 ` CVE-2024-26908: x86/xen: Add some null pointer checking to smp.c 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
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=f73bb0fe-9ba6-46de-8732-bd372438068e@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 \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).