From: Greg KH <gregkh@linuxfoundation.org>
To: Juergen Gross <jgross@suse.com>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: CVE-2023-53502: xen/netback: Fix buffer overrun triggered by unusual packet
Date: Wed, 1 Oct 2025 15:07:59 +0200 [thread overview]
Message-ID: <2025100103-helpline-finishing-055f@gregkh> (raw)
In-Reply-To: <bca10ff3-75d2-4063-a323-8881d8baa3c1@suse.com>
On Wed, Oct 01, 2025 at 02:05:47PM +0200, Juergen Gross wrote:
> On 01.10.25 13:45, Greg Kroah-Hartman wrote:
> > From: Greg Kroah-Hartman <gregkh@kernel.org>
> >
> > Description
> > ===========
> >
> > In the Linux kernel, the following vulnerability has been resolved:
> >
> > xen/netback: Fix buffer overrun triggered by unusual packet
> >
> > It is possible that a guest can send a packet that contains a head + 18
> > slots and yet has a len <= XEN_NETBACK_TX_COPY_LEN. This causes nr_slots
> > to underflow in xenvif_get_requests() which then causes the subsequent
> > loop's termination condition to be wrong, causing a buffer overrun of
> > queue->tx_map_ops.
> >
> > Rework the code to account for the extra frag_overflow slots.
> >
> > This is CVE-2023-34319 / XSA-432.
> >
> > The Linux kernel CVE team has assigned CVE-2023-53502 to this issue.
>
> As can be seen right above your line "The Linux kernel CVE team ..."
> this issue has been handled by the Xen security team already and a
> CVE is assigned since then.
Ugh, then why doesn't that CVE reference this commit properly? I do
sweep all old CVE assignments when doing this old-rereview. Any chance
you can go and update these CVE entries with the proper git ids?
> Please revoke your CVE assignment.
Will go do so now, thanks for catching this.
greg k-h
prev parent reply other threads:[~2025-10-01 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2025100127-CVE-2023-53502-aa6a@gregkh>
2025-10-01 12:05 ` Juergen Gross
2025-10-01 13:07 ` 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=2025100103-helpline-finishing-055f@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
all inboxes | Powered by JetHome®