From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
dtatulea@nvidia.com, gal@nvidia.com, leon@kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
mbloch@nvidia.com, saeedm@nvidia.com, ychemla@nvidia.com
Subject: Re: [PATCH net] net/mlx5: E-Switch: fix use-after-free in mlx5_eswitch_termtbl_put
Date: Sat, 05 Sep 2026 20:30:12 +0000 [thread overview]
Message-ID: <178864021214.1345393.10049217548777927998.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260902193514.3668880-1-tariqt@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 2 Sep 2026 22:35:14 +0300 you wrote:
> From: Yael Chemla <ychemla@nvidia.com>
>
> In mlx5_eswitch_termtbl_put(), the zero-ref cleanup check reads
> tt->ref_count after termtbl_mutex has been released. Two concurrent
> callers on the same mlx5_termtbl_handle race: one decrements ref_count
> to zero, removes the hash entry, and calls kfree(tt) while the other
> has already dropped the mutex and is about to evaluate
> if (!tt->ref_count), producing a use-after-free.
>
> [...]
Here is the summary with links:
- [net] net/mlx5: E-Switch: fix use-after-free in mlx5_eswitch_termtbl_put
https://git.kernel.org/netdev/net/c/7ee07f601f8f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-05 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 19:35 [PATCH net] net/mlx5: E-Switch: fix use-after-free in mlx5_eswitch_termtbl_put Tariq Toukan
2026-09-05 20: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=178864021214.1345393.10049217548777927998.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=ychemla@nvidia.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.