From: Simon Horman <horms@kernel.org>
To: Hyunwoo Kim <imv4bel@gmail.com>
Cc: john.fastabend@gmail.com, kuba@kernel.org, sd@queasysnail.net,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net v2] tls: Fix race condition in tls_sw_cancel_work_tx()
Date: Sun, 22 Feb 2026 17:44:45 +0000 [thread overview]
Message-ID: <aZtAjSf-iw-85UU2@horms.kernel.org> (raw)
In-Reply-To: <aZgsFO6nfylfvLE7@v4bel>
On Fri, Feb 20, 2026 at 06:40:36PM +0900, Hyunwoo Kim wrote:
> This issue was discovered during a code audit.
>
> After cancel_delayed_work_sync() is called from tls_sk_proto_close(),
> tx_work_handler() can still be scheduled from paths such as the
> Delayed ACK handler or ksoftirqd.
> As a result, the tx_work_handler() worker may dereference a freed
> TLS object.
>
> The following is a simple race scenario:
>
> cpu0 cpu1
>
> tls_sk_proto_close()
> tls_sw_cancel_work_tx()
> tls_write_space()
> tls_sw_write_space()
> if (!test_and_set_bit(BIT_TX_SCHEDULED, &tx_ctx->tx_bitmask))
> set_bit(BIT_TX_SCHEDULED, &ctx->tx_bitmask);
> cancel_delayed_work_sync(&ctx->tx_work.work);
> schedule_delayed_work(&tx_ctx->tx_work.work, 0);
>
> To prevent this race condition, cancel_delayed_work_sync() is
> replaced with disable_delayed_work_sync().
>
> Fixes: f87e62d45e51 ("net/tls: remove close callback sock unlock/lock around TX work flush")
> Signed-off-by: Hyunwoo Kim <imv4bel@gmail.com>
> ---
> Changes in v2:
> - Shorten the patch subject
> - Target the net tree
> - Add the bug discovery background and the race scenario to the commit message
> - v1: https://lore.kernel.org/all/aZLotq3aZY0b-dI8@v4bel/
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2026-02-22 17:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 9:40 [PATCH net v2] tls: Fix race condition in tls_sw_cancel_work_tx() Hyunwoo Kim
2026-02-22 17:44 ` Simon Horman [this message]
2026-02-23 16:18 ` Sabrina Dubroca
2026-02-24 1:30 ` patchwork-bot+netdevbpf
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=aZtAjSf-iw-85UU2@horms.kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=imv4bel@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
/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.