All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Xin Long <lucien.xin@gmail.com>
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
	davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
	pabeni@redhat.com, horms@kernel.org, marcelo.leitner@gmail.com,
	tlatkdgus1@gmail.com
Subject: Re: [PATCH net] sctp: validate SACK pull length against chunk length, not skb length
Date: Tue, 17 Nov 2026 00:20:06 +0000	[thread overview]
Message-ID: <179487480652.257811.15441708488067706931.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <3fbf59d17a91c46098e3d4115e06987918b68c45.1794495702.git.lucien.xin@gmail.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 12 Nov 2026 10:01:42 -0500 you wrote:
> sctp_sm_pull_sack() derives its pull length from the num_gap_ack_blocks
> and num_dup_tsns fields in the SACK body, but validates it against
> chunk->skb->len (the remaining packet data) rather than the SACK chunk's
> declared length. A malformed SACK with an inflated num_dup_tsns can pass
> this check when subsequent chunks pad the skb, advancing skb->data past
> the SACK boundary into later chunks.
> 
> [...]

Here is the summary with links:
  - [net] sctp: validate SACK pull length against chunk length, not skb length
    https://git.kernel.org/netdev/net/c/533ec433efdc

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  reply	other threads:[~2026-11-17  0:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12 15:01 [PATCH net] sctp: validate SACK pull length against chunk length, not skb length Xin Long
2026-11-17  0:20 ` patchwork-bot+netdevbpf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-11-12 15:08 netdev-bot+sinfo

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=179487480652.257811.15441708488067706931.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@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 \
    --cc=tlatkdgus1@gmail.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 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.