All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, netdev@vger.kernel.org,
	syzbot+a3f21220cbbb6e14ee2e@syzkaller.appspotmail.com,
	steffen.klassert@secunet.com, herbert@gondor.apana.org.au
Subject: Re: [PATCH net] xfrm: iptfs: fix skb leak on error in __input_process_payload()
Date: Tue, 03 Nov 2026 11:40:04 +0000	[thread overview]
Message-ID: <179370600414.1068298.8102080811315201623.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261030083358.2653599-1-edumazet@kernel.org>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Fri, 30 Oct 2026 09:33:58 +0100 you wrote:
> syzbot reported a memory leak of the received skb (and its sec_path
> extension) in the IP-TFS receive path.
> 
> __input_process_payload() parses the inner packets of an IP-TFS payload
> and queues them on @sublist, which is only sent after the parsing loop.
> Three error paths inside the loop (skb_copy_seq_read() failure, invalid
> inner IPv4 header length, unknown IP version) jump to the "done" label,
> which is placed after the code sending @sublist.
> 
> [...]

Here is the summary with links:
  - [net] xfrm: iptfs: fix skb leak on error in __input_process_payload()
    https://git.kernel.org/netdev/net/c/64e45ed926cd

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-11-03 11:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30  8:33 [PATCH net] xfrm: iptfs: fix skb leak on error in __input_process_payload() Eric Dumazet
2026-11-03  8:45 ` Paolo Abeni
2026-11-03 10:51   ` Steffen Klassert
2026-11-03  9:59     ` Paolo Abeni
2026-11-03 11:15       ` Steffen Klassert
2026-11-03 11:40 ` patchwork-bot+netdevbpf [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=179370600414.1068298.8102080811315201623.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=steffen.klassert@secunet.com \
    --cc=syzbot+a3f21220cbbb6e14ee2e@syzkaller.appspotmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.