All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Aldo Ariel Panzardo <qwe.aldo@gmail.com>
Cc: jk@codeconstruct.com.au, matt@codeconstruct.com.au,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: mctp: hold a reference to the route device in mctp_route_lookup()
Date: Thu, 20 Aug 2026 19:30:33 +0000	[thread overview]
Message-ID: <178725423364.446762.16328588855452508524.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260813022102.2792032-1-qwe.aldo@gmail.com>

Hello:

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

On Wed, 12 Aug 2026 23:21:02 -0300 you wrote:
> mctp_route_lookup() uses rt->dev without holding a reference on it.
> mctp_route_lookup_single() returns the route under RCU only, so the
> route's device can be torn down concurrently: mctp_dev_put() drops the
> last reference and synchronously kfree()s mdev->addrs.  mctp_dev_saddr()
> then reads rt->dev->addrs[0], giving a use-after-free reachable by an
> unprivileged local AF_MCTP user on the receive/forwarding path (no
> CAP_NET_RAW required):
> 
> [...]

Here is the summary with links:
  - net: mctp: hold a reference to the route device in mctp_route_lookup()
    https://git.kernel.org/netdev/net/c/408da1df1811

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-08-20 19:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13  2:21 [PATCH] net: mctp: hold a reference to the route device in mctp_route_lookup() Aldo Ariel Panzardo
2026-08-14  2:19 ` Jeremy Kerr
2026-08-17 12:14   ` Yiqi Sun
2026-08-20 20:13     ` Aldo Ariel Panzardo
2026-08-20 19: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=178725423364.446762.16328588855452508524.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jk@codeconstruct.com.au \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@codeconstruct.com.au \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=qwe.aldo@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.