From: patchwork-bot+netdevbpf@kernel.org
To: Votokina Victoria <Victoria.Votokina@kaspersky.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, tglx@kernel.org,
mingo@kernel.org, eric.lapuyade@linux.intel.com,
sameo@linux.intel.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: [PATCH] nfc: hci: shdlc: Stop timers and work before freeing context
Date: Fri, 06 Feb 2026 03:00:04 +0000 [thread overview]
Message-ID: <177034680483.662298.10040199384768030642.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260203113158.2008723-1-Victoria.Votokina@kaspersky.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 3 Feb 2026 14:31:57 +0300 you wrote:
> llc_shdlc_deinit() purges SHDLC skb queues and frees the llc_shdlc
> structure while its timers and state machine work may still be active.
>
> Timer callbacks can schedule sm_work, and sm_work accesses SHDLC state
> and the skb queues. If teardown happens in parallel with a queued/running
> work item, it can lead to UAF and other shutdown races.
>
> [...]
Here is the summary with links:
- nfc: hci: shdlc: Stop timers and work before freeing context
https://git.kernel.org/netdev/net/c/c9efde1e537b
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-02-06 3:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 11:31 [PATCH] nfc: hci: shdlc: Stop timers and work before freeing context Votokina Victoria
2026-02-06 3:00 ` 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=177034680483.662298.10040199384768030642.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Victoria.Votokina@kaspersky.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.lapuyade@linux.intel.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sameo@linux.intel.com \
--cc=tglx@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox