From: Juergen Gross <jgross@suse.com>
To: 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 14:05:47 +0200 [thread overview]
Message-ID: <bca10ff3-75d2-4063-a323-8881d8baa3c1@suse.com> (raw)
In-Reply-To: <2025100127-CVE-2023-53502-aa6a@gregkh>
[-- Attachment #1.1.1: Type: text/plain, Size: 1000 bytes --]
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.
Please revoke your CVE assignment.
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:[~2025-10-01 12:05 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 [this message]
2025-10-01 13:07 ` 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=bca10ff3-75d2-4063-a323-8881d8baa3c1@suse.com \
--to=jgross@suse.com \
--cc=cve@kernel.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
all inboxes | Powered by JetHome®