public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Mingyu Wang <25181214217@stu.xidian.edu.cn>,
	 willemdebruijn.kernel@gmail.com,  davem@davemloft.net,
	 dsahern@kernel.org,  edumazet@google.com,  kuba@kernel.org,
	 pabeni@redhat.com
Cc: sd@queasysnail.net,  horms@kernel.org,  netdev@vger.kernel.org,
	 linux-kernel@vger.kernel.org,
	 Mingyu Wang <25181214217@stu.xidian.edu.cn>,
	 syzbot+e5d6936b9f4545fd88ab@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] ipv6: fix memory leak in __ip6_make_skb() when queue is empty
Date: Thu, 23 Apr 2026 10:59:45 -0400	[thread overview]
Message-ID: <willemdebruijn.kernel.28284ffff84dc@gmail.com> (raw)
In-Reply-To: <20260423082233.514056-1-25181214217@stu.xidian.edu.cn>

Mingyu Wang wrote:
> During fuzzing with failslab enabled, a memory leak was observed in the
> IPv6 UDP send path.
> 
> The root cause resides in __ip6_make_skb(). In extremely rare cases
> (such as fault injection or specific empty payload conditions),

Can you elaborate on this? Which fault injection lets
__ip6_append_data succeed without writing data?

> __ip6_append_data() may succeed but leave the socket's write queue
> empty.
> 
> When __ip6_make_skb() is subsequently called, __skb_dequeue(queue)
> returns NULL. The previous logic handled this by executing a 'goto out;',
> which completely bypassed the call to ip6_cork_release(cork).
> 
> Since the 'cork' structure actively holds a reference to the routing
> entry (dst_entry) and potentially other allocated options, skipping
> the release cleanly leaks these resources.
> 
> Fix this by introducing an 'out_cork_release' label and jumping to it
> when skb is NULL, ensuring the cork state is always properly cleaned up.
> The now-unused 'out' label is also removed to prevent compiler warnings.
> 
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")

I think this is 

Fixes: 6422398c2ab0 ("ipv6: introduce ipv6_make_skb")

> Reported-by: syzbot+e5d6936b9f4545fd88ab@syzkaller.appspotmail.com
> Signed-off-by: Mingyu Wang <25181214217@stu.xidian.edu.cn>

  parent reply	other threads:[~2026-04-23 14:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23  8:22 [PATCH v2] ipv6: fix memory leak in __ip6_make_skb() when queue is empty Mingyu Wang
2026-04-23  8:23 ` syzbot
2026-04-23 14:59 ` Willem de Bruijn [this message]
2026-04-23 14:59   ` syzbot
2026-04-24  3:16   ` 王明煜
2026-04-24  3:16     ` syzbot
2026-04-24  3:26     ` 王明煜
2026-04-24  3:27       ` syzbot
2026-04-24  6:56       ` Bezdeka, Florian
2026-04-24  6:56         ` syzbot
2026-04-24 15:40         ` 王明煜
2026-04-24 15:40           ` syzbot

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=willemdebruijn.kernel.28284ffff84dc@gmail.com \
    --to=willemdebruijn.kernel@gmail.com \
    --cc=25181214217@stu.xidian.edu.cn \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sd@queasysnail.net \
    --cc=syzbot+e5d6936b9f4545fd88ab@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox