kernel_samsung_a53x/drivers/net/xen-netback
Jan Beulich d4180781e9 xen-netback: don't produce zero-size SKB frags
commit c7ec4f2d684e17d69bbdd7c4324db0ef5daac26a upstream.

While frontends may submit zero-size requests (wasting a precious slot),
core networking code as of at least 3ece782693c4b ("sock: skb_copy_ubufs
support for compound pages") can't deal with SKBs when they have all
zero-size fragments. Respond to empty requests right when populating
fragments; all further processing is fragment based and hence won't
encounter these empty requests anymore.

In a way this should have been that way from the beginning: When no data
is to be transferred for a particular request, there's not even a point
in validating the respective grant ref. That's no different from e.g.
passing NULL into memcpy() when at the same time the size is 0.

This is XSA-448 / CVE-2023-46838.

Cc: stable@vger.kernel.org
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Reviewed-by: Paul Durrant <paul@xen.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2024-11-18 12:12:45 +01:00
..
common.h Import A536BXXU9EXDC 2024-06-15 16:02:09 -03:00
hash.c Import A536BXXU9EXDC 2024-06-15 16:02:09 -03:00
interface.c xen-netback: use default TX queue size for vifs 2024-11-08 11:25:45 +01:00
Makefile Import A536BXXU9EXDC 2024-06-15 16:02:09 -03:00
netback.c xen-netback: don't produce zero-size SKB frags 2024-11-18 12:12:45 +01:00
rx.c Import A536BXXU9EXDC 2024-06-15 16:02:09 -03:00
xenbus.c Import A536BXXU9EXDC 2024-06-15 16:02:09 -03:00