Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ren Wei <enjou1224z@gmail.com>
Cc: netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
	jmaloy@redhat.com, davem@davemloft.net, edumazet@google.com,
	pabeni@redhat.com, horms@kernel.org, ying.xue@windriver.com,
	tuong.t.lien@dektech.com.au, vega@nebusec.ai, zihanx@nebusec.ai
Subject: Re: [PATCH net v3 0/1] tipc: avoid use-after-free in poll trace queue dumps
Date: Mon, 27 Jul 2026 22:40:18 +0000	[thread overview]
Message-ID: <178519201863.1443317.8809298946831933407.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1784794294.git.zihanx@nebusec.ai>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 24 Jul 2026 00:38:40 +0800 you wrote:
> From: Zihan Xi <zihanx@nebusec.ai>
> 
> Hi Linux kernel maintainers,
> 
> We found and validated a bug in net/tipc/socket.c. The bug is
> reachable by a local process that can create TIPC sockets and enable
> TIPC tracepoints. We've rebuilt and rerun the reproducer with the
> updated fix, and the crash no longer reproduces.
> 
> [...]

Here is the summary with links:
  - [net,v3,1/1] tipc: avoid use-after-free in poll trace queue dumps
    https://git.kernel.org/netdev/net/c/b4f1719dfea0

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-07-27 22:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23 16:38 [PATCH net v3 0/1] tipc: avoid use-after-free in poll trace queue dumps Ren Wei
2026-07-23 16:38 ` [PATCH net v3 1/1] " Ren Wei
2026-07-27  1:59   ` Tung Quang Nguyen
2026-07-27 22: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=178519201863.1443317.8809298946831933407.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=enjou1224z@gmail.com \
    --cc=horms@kernel.org \
    --cc=jmaloy@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=tuong.t.lien@dektech.com.au \
    --cc=vega@nebusec.ai \
    --cc=ying.xue@windriver.com \
    --cc=zihanx@nebusec.ai \
    /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