All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Michael Bommarito <michael.bommarito@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
	fmaurer@redhat.com, bigeasy@linutronix.de, luka.gejak@linux.dev,
	xiyou.wangcong@gmail.com, kexinsun@smail.nju.edu.cn,
	stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/1] net: hsr: fix node-table UAF on device teardown
Date: Sat, 16 May 2026 01:40:05 +0000	[thread overview]
Message-ID: <177889560589.219555.12152803144106381021.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260513233838.3064715-1-michael.bommarito@gmail.com>

Hello:

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

On Wed, 13 May 2026 19:38:37 -0400 you wrote:
> Hi,
> 
> HSR generic-netlink node-list/status readers walk hsr->node_db under
> rcu_read_lock(), but RTM_DELLINK teardown frees the same node table
> immediately via plain list_del() + kfree(). A reader that has already
> obtained a struct hsr_node can race hsr_dellink() and dereference
> freed node memory.
> 
> [...]

Here is the summary with links:
  - [net,1/1] net: hsr: defer node table free until after RCU readers
    https://git.kernel.org/netdev/net/c/aaec7096f996

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-05-16  1:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13 23:38 [PATCH net 0/1] net: hsr: fix node-table UAF on device teardown Michael Bommarito
2026-05-13 23:38 ` [PATCH net 1/1] net: hsr: defer node table free until after RCU readers Michael Bommarito
2026-05-16  1: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=177889560589.219555.12152803144106381021.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fmaurer@redhat.com \
    --cc=horms@kernel.org \
    --cc=kexinsun@smail.nju.edu.cn \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luka.gejak@linux.dev \
    --cc=michael.bommarito@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.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.