From: patchwork-bot+netdevbpf@kernel•org
To: Dmitry Antipov <dmantipov@yandex•ru>
Cc: lucien.xin@gmail•com, kuba@kernel•org, marcelo.leitner@gmail•com,
linux-sctp@vger•kernel.org, netdev@vger•kernel.org,
lvc-project@linuxtesting•org,
syzbot+8bb053b5d63595ab47db@syzkaller•appspotmail.com
Subject: Re: [PATCH] [v3] net: sctp: fix skb leak in sctp_inq_free()
Date: Thu, 15 Feb 2024 16:00:30 +0000 [thread overview]
Message-ID: <170801283096.9967.10675822819256962996.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240214082224.10168-1-dmantipov@yandex.ru>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Wed, 14 Feb 2024 11:22:24 +0300 you wrote:
> In case of GSO, 'chunk->skb' pointer may point to an entry from
> fraglist created in 'sctp_packet_gso_append()'. To avoid freeing
> random fraglist entry (and so undefined behavior and/or memory
> leak), introduce 'sctp_inq_chunk_free()' helper to ensure that
> 'chunk->skb' is set to 'chunk->head_skb' (i.e. fraglist head)
> before calling 'sctp_chunk_free()', and use the aforementioned
> helper in 'sctp_inq_pop()' as well.
>
> [...]
Here is the summary with links:
- [v3] net: sctp: fix skb leak in sctp_inq_free()
https://git.kernel.org/netdev/net/c/4e45170d9acc
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:[~2024-02-15 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 8:22 [PATCH] [v3] net: sctp: fix skb leak in sctp_inq_free() Dmitry Antipov
2024-02-14 19:14 ` Xin Long
2024-02-15 16: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=170801283096.9967.10675822819256962996.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=dmantipov@yandex$(echo .)ru \
--cc=kuba@kernel$(echo .)org \
--cc=linux-sctp@vger$(echo .)kernel.org \
--cc=lucien.xin@gmail$(echo .)com \
--cc=lvc-project@linuxtesting$(echo .)org \
--cc=marcelo.leitner@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=syzbot+8bb053b5d63595ab47db@syzkaller$(echo .)appspotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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