From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?SsOpcsOpbXkgSmVhbiA8SmVyZW15LkplYW5Ab3NzLmN5YmVyLmdvdXYuZnI+?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: sd@queasysnail.net, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net v2] macsec: prevent AES-GCM nonce reuse after packet number wrap
Date: Fri, 16 Oct 2026 01:00:13 +0000 [thread overview]
Message-ID: <179211241301.4182913.3552458253132943260.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261008080625.360063-2-Jeremy.Jean@oss.cyber.gouv.fr>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 8 Oct 2026 08:06:26 +0000 you wrote:
> After allocating the last valid packet number, MACsec wraps next_pn to
> zero and deactivates the transmit SA. This happens for both 32- and
> 64-bit types of packet numbers (at values 0xffffffff and
> 0xffffffffffffffff, respectively).
>
> TX packets that were still getting processed during deactivation keep
> being processed and then receive packet numbers. The first gets 0 and
> is correctly dropped, but next_pn is incremented to 1, which makes the
> next packet take number 1. It then does not get dropped and may induce
> a reuse of the AES-GCM nonce corresponding to value 1.
>
> [...]
Here is the summary with links:
- [net,v2] macsec: prevent AES-GCM nonce reuse after packet number wrap
https://git.kernel.org/netdev/net-next/c/94d51c59f0a8
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-10-16 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 8:06 [PATCH net v2] macsec: prevent AES-GCM nonce reuse after packet number wrap Jérémy Jean
2026-10-08 8:15 ` netdev-bot+sinfo
2026-10-16 1: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=179211241301.4182913.3552458253132943260.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?SsOpcsOpbXkgSmVhbiA8SmVyZW15LkplYW5Ab3NzLmN5YmVyLmdvdXYuZnI+?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=stable@vger.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