From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Juergen Gross <jgross@suse.com>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: CVE-2024-47722: xen: use correct end address of kernel for conflict checking
Date: Mon, 21 Oct 2024 14:58:14 +0200 [thread overview]
Message-ID: <2024102152-stinky-tiger-4e51@gregkh> (raw)
In-Reply-To: <11213aab-7ef9-474e-8ada-6397a7e74d7b@suse.com>
On Mon, Oct 21, 2024 at 02:35:16PM +0200, Juergen Gross wrote:
> On 21.10.24 14:16, Greg Kroah-Hartman wrote:
> > Description
> > ===========
> >
> > In the Linux kernel, the following vulnerability has been resolved:
> >
> > xen: use correct end address of kernel for conflict checking
> >
> > When running as a Xen PV dom0 the kernel is loaded by the hypervisor
> > using a different memory map than that of the host. In order to
> > minimize the required changes in the kernel, the kernel adapts its
> > memory map to that of the host. In order to do that it is checking
> > for conflicts of its load address with the host memory map.
> >
> > Unfortunately the tested memory range does not include the .brk
> > area, which might result in crashes or memory corruption when this
> > area does conflict with the memory map of the host.
> >
> > Fix the test by using the _end label instead of __bss_stop.
> >
> > The Linux kernel CVE team has assigned CVE-2024-47722 to this issue.
>
> I fail to see how an unprivileged user could cause any harm here.
>
> This bug is affecting the guest only, so only the guest admin can cause
> harm to the guest at will via a special kernel. IMHO nothing CVE-worthy
> here.
Ah, I thought this could affect the host, sorry about that.
> So I'd like to ask for this CVE being revoked.
Now revoked!
thanks for the review.
greg k-h
prev parent reply other threads:[~2024-10-21 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024102103-CVE-2024-47722-dc6e@gregkh>
2024-10-21 12:35 ` CVE-2024-47722: xen: use correct end address of kernel for conflict checking Juergen Gross
2024-10-21 12:58 ` Greg Kroah-Hartman [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=2024102152-stinky-tiger-4e51@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=jgross@suse.com \
--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