From: patchwork-bot+netdevbpf@kernel.org
To: Jaeyeong Lee <lee@jaeyeong.cc>
Cc: netdev@vger.kernel.org, john.fastabend@gmail.com,
kuba@kernel.org, sd@queasysnail.net, davem@davemloft.net,
edumazet@kernel.org, pabeni@redhat.com, horms@kernel.org,
alice.kernel@fastmail.im, tariqt@nvidia.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net] net/tls: serialize context removal in tls_device_down()
Date: Tue, 17 Nov 2026 14:50:05 +0000 [thread overview]
Message-ID: <179492700528.635190.1108444356171254276.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261112043209.102404-1-lee@jaeyeong.cc>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 12 Nov 2026 04:32:17 +0000 you wrote:
> tls_device_down() moves each context to tls_device_down_list while
> holding tls_device_lock. It then drops its reference and removes the
> context after releasing the lock.
>
> tls_device_queue_ctx_destruction() removes contexts from the same list
> under tls_device_lock. If it removes an adjacent context while
> tls_device_down() is deleting its node, the two list updates can
> interleave. One update can then target a context freed by the other path,
> causing a use-after-free write.
>
> [...]
Here is the summary with links:
- [net] net/tls: serialize context removal in tls_device_down()
https://git.kernel.org/netdev/net/c/81c8333141b9
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-11-17 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 4:32 [PATCH net] net/tls: serialize context removal in tls_device_down() Jaeyeong Lee
2026-11-17 14:50 ` 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=179492700528.635190.1108444356171254276.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alice.kernel@fastmail.im \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=lee@jaeyeong.cc \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=stable@vger.kernel.org \
--cc=tariqt@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.