diff options
| author | Josef Bacik <josef@toxicpanda.com> | 2026-10-07 17:57:32 +0000 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-10-08 11:00:01 -0700 |
| commit | 93ccaf1c26e2133396173b76a071e59024daa622 (patch) | |
| tree | 4e49a3d06692a62bcfd603de3a584be2b521ac6a /tools/lib/python/kdoc/python_version.py | |
| parent | 513e23857a3a64fa73a1deb36a385eecd4ad7690 (diff) | |
| download | linux-next-93ccaf1c26e2133396173b76a071e59024daa622.tar.gz linux-next-93ccaf1c26e2133396173b76a071e59024daa622.zip | |
xen/netfront: don't leak the skb when xennet_fill_frags() fails
When a response chain has more slots than fit in the skb's frags,
xennet_fill_frags() returns an error and xennet_poll() jumps to its
error path. That path moves what's left on tmpq to errq to be freed,
but the skb being filled was already dequeued from tmpq, so it's never
freed. Each chain that overflows leaks the skb and the pages attached
to it as frags, and the backend decides how many slots it sends.
Put the skb back on tmpq before taking the error path, like the
xennet_set_skb_gso() failure just above it does.
Fixes: ad4f15dc2c70 ("xen/netfront: don't bug in case of too many frags")
Cc: stable@vger.kernel.org
Signed-off-by: Josef Bacik <josef@toxicpanda.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Link: https://patch.msgid.link/20261007-b4-xen-netfront-fill-frags-leak-v1-1-a8a01ff9cd52@toxicpanda.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions