From: patchwork-bot+netdevbpf@kernel.org
To: Junrui Luo <moonafterrain@outlook.com>
Cc: sd@queasysnail.net, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
mayflowerera@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, danisjiang@gmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH net] macsec: fix replay protection at XPN lower-PN wrap
Date: Mon, 25 May 2026 20:00:08 +0000 [thread overview]
Message-ID: <177973920864.3098866.2633413254433514434.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <SYBPR01MB78813FD49E58F253B989F197AF012@SYBPR01MB7881.ausprd01.prod.outlook.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 20 May 2026 11:47:55 +0800 you wrote:
> In macsec_post_decrypt(), when pn is U32_MAX, pn + 1 overflows u32 to 0
> and the first branch never fires. If next_pn_halves.lower is also in the
> upper half, pn_same_half(pn, lower) is true and the XPN else-if does not
> fire either, leaving next_pn_halves unchanged. An attacker that captures
> the legitimate frame carrying pn == 0xFFFFFFFF on an XPN association
> can then replay it indefinitely, since lowest_pn never rises above
> the captured pn and macsec_decrypt() reconstructs the same IV.
>
> [...]
Here is the summary with links:
- [net] macsec: fix replay protection at XPN lower-PN wrap
https://git.kernel.org/netdev/net/c/e68842b33564
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-05-25 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 3:47 [PATCH net] macsec: fix replay protection at XPN lower-PN wrap Junrui Luo
2026-05-25 20: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=177973920864.3098866.2633413254433514434.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=danisjiang@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mayflowerera@gmail.com \
--cc=moonafterrain@outlook.com \
--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