From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?SsOpcsOpbXkgSmVhbiA8SmVyZW15LkplYW5Ab3NzLmN5YmVyLmdvdXYuZnI+?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: marcelo.leitner@gmail.com, lucien.xin@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, linux-sctp@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sctp: validate cookie AUTH state before use
Date: Fri, 07 Aug 2026 22:40:05 +0000 [thread overview]
Message-ID: <178614240590.2445639.1288172802373951589.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260804200042.2412009-1-Jeremy.Jean@oss.cyber.gouv.fr>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 4 Aug 2026 20:00:42 +0000 you wrote:
> When cookie authentication is disabled, COOKIE_ECHO restores fixed-size
> AUTH fields directly from peer-controlled cookie bytes. A forged RANDOM
> length, HMAC list, or CHUNKS list can then reach association consumers
> with lengths or identifiers that were never validated against the local
> backing arrays.
>
> A forged RANDOM length can cause out-of-bounds reads during key-vector
> construction. A forged HMAC identifier also caused a 32-byte write past
> a zero-length AUTH chunk, providing a primitive for a local privilege
> escalation chain.
>
> [...]
Here is the summary with links:
- sctp: validate cookie AUTH state before use
https://git.kernel.org/netdev/net/c/3dbb44d88b1e
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-08-07 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 20:00 Jérémy Jean
2026-08-07 18:47 ` Xin Long
2026-08-07 18:49 ` Xin Long
2026-08-07 22:40 ` 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=178614240590.2445639.1288172802373951589.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=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®