Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: dsahern@kernel.org, idosch@nvidia.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, amcohen@nvidia.com, jiri@resnulli.us,
	kuni1840@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH v1 net 0/2] net: fib: Fix two use-after-free in drivers during RCU dump.
Date: Thu, 11 Jun 2026 22:30:17 +0000	[thread overview]
Message-ID: <178121701713.389578.16845185284597284885.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260610061744.2030996-1-kuniyu@google.com>

Hello:

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

On Wed, 10 Jun 2026 06:17:17 +0000 you wrote:
> syzbot reported fib_info UAF in netdevsim, and the same bug
> exists in rocker and mlxsw.
> 
> Patch 1 fixes it, and Patch 2 fixes the same type of bug of
> fib_rule.
> 
> 
> [...]

Here is the summary with links:
  - [v1,net,1/2] ipv4: fib: Don't dump dying fib_info in fib_leaf_notify().
    https://git.kernel.org/netdev/net/c/06b693d2eb66
  - [v1,net,2/2] net: fib_rules: Don't dump dying fib_rule in fib_rules_dump().
    https://git.kernel.org/netdev/net/c/2821e85c058f

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-06-11 22:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10  6:17 [PATCH v1 net 0/2] net: fib: Fix two use-after-free in drivers during RCU dump Kuniyuki Iwashima
2026-06-10  6:17 ` [PATCH v1 net 1/2] ipv4: fib: Don't dump dying fib_info in fib_leaf_notify() Kuniyuki Iwashima
2026-06-11 12:33   ` Ido Schimmel
2026-06-11 14:30   ` David Ahern
2026-06-10  6:17 ` [PATCH v1 net 2/2] net: fib_rules: Don't dump dying fib_rule in fib_rules_dump() Kuniyuki Iwashima
2026-06-11 12:33   ` Ido Schimmel
2026-06-11 14:30   ` David Ahern
2026-06-11 22:30 ` 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=178121701713.389578.16845185284597284885.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=amcohen@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=kuni1840@gmail.com \
    --cc=kuniyu@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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