All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	netdev@vger.kernel.org, eric.dumazet@gmail.com,
	syzbot+1939f24bdb783e9e43d9@syzkaller.appspotmail.com,
	vladimir.oltean@nxp.com
Subject: Re: [PATCH net] net: avoid potential UAF in default_operstate()
Date: Thu, 05 Dec 2024 11:00:33 +0000	[thread overview]
Message-ID: <173339643375.1549157.2163133507378717165.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241203170933.2449307-1-edumazet@google.com>

Hello:

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

On Tue,  3 Dec 2024 17:09:33 +0000 you wrote:
> syzbot reported an UAF in default_operstate() [1]
> 
> Issue is a race between device and netns dismantles.
> 
> After calling __rtnl_unlock() from netdev_run_todo(),
> we can not assume the netns of each device is still alive.
> 
> [...]

Here is the summary with links:
  - [net] net: avoid potential UAF in default_operstate()
    https://git.kernel.org/netdev/net/c/750e51603395

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



      parent reply	other threads:[~2024-12-05 11:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 17:09 [PATCH net] net: avoid potential UAF in default_operstate() Eric Dumazet
2024-12-03 17:37 ` Vladimir Oltean
2024-12-03 17:56   ` Eric Dumazet
2024-12-04 11:41     ` Vladimir Oltean
2024-12-04 11:46       ` Eric Dumazet
2024-12-04 12:57         ` Vladimir Oltean
2024-12-04 13:38           ` Eric Dumazet
2024-12-04 14:34             ` Vladimir Oltean
2024-12-04 14:35 ` Vladimir Oltean
2024-12-05 11:00 ` 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=173339643375.1549157.2163133507378717165.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+1939f24bdb783e9e43d9@syzkaller.appspotmail.com \
    --cc=vladimir.oltean@nxp.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.