From: patchwork-bot+netdevbpf@kernel.org
To: David Howells <dhowells@redhat.com>
Cc: netdev@vger.kernel.org, marc.dionne@auristor.com,
kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org, anderson@allelesecurity.com,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2 0/6] rxrpc: Miscellaneous fixes
Date: Thu, 23 Apr 2026 19:50:13 +0000 [thread overview]
Message-ID: <177697381355.740120.3673972749152907468.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260422161438.2593376-1-dhowells@redhat.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 22 Apr 2026 17:14:29 +0100 you wrote:
> Here are some fixes for rxrpc, as found by Sashiko[1]:
>
> (1) Fix leaks in rxkad_verify_response().
>
> (2) Fix handling of rxkad-encrypted packets with crypto-misaligned
> lengths.
>
> [...]
Here is the summary with links:
- [net,v2,1/6] rxrpc: Fix memory leaks in rxkad_verify_response()
https://git.kernel.org/netdev/net/c/34f61a07e0cd
- [net,v2,2/6] rxrpc: Fix rxkad crypto unalignment handling
https://git.kernel.org/netdev/net/c/def304aae2ed
- [net,v2,3/6] rxrpc: Fix potential UAF after skb_unshare() failure
https://git.kernel.org/netdev/net/c/1f2740150f90
- [net,v2,4/6] rxrpc: Fix conn-level packet handling to unshare RESPONSE packets
https://git.kernel.org/netdev/net/c/24481a7f5733
- [net,v2,5/6] rxgk: Fix potential integer overflow in length check
https://git.kernel.org/netdev/net/c/6929350080f4
- [net,v2,6/6] rxrpc: Fix missing validation of ticket length in non-XDR key preparsing
https://git.kernel.org/netdev/net/c/ac33733b10b4
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-04-23 19:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 16:14 [PATCH net v2 0/6] rxrpc: Miscellaneous fixes David Howells
2026-04-22 16:14 ` [PATCH net v2 1/6] rxrpc: Fix memory leaks in rxkad_verify_response() David Howells
2026-04-22 16:14 ` [PATCH net v2 2/6] rxrpc: Fix rxkad crypto unalignment handling David Howells
2026-04-22 16:14 ` [PATCH net v2 3/6] rxrpc: Fix potential UAF after skb_unshare() failure David Howells
2026-04-22 16:14 ` [PATCH net v2 4/6] rxrpc: Fix conn-level packet handling to unshare RESPONSE packets David Howells
2026-04-22 16:14 ` [PATCH net v2 5/6] rxgk: Fix potential integer overflow in length check David Howells
2026-04-22 16:14 ` [PATCH net v2 6/6] rxrpc: Fix missing validation of ticket length in non-XDR key preparsing David Howells
2026-04-23 17:56 ` [PATCH net v2 0/6] rxrpc: Miscellaneous fixes Jakub Kicinski
2026-04-23 18:47 ` David Howells
2026-04-23 18:58 ` Jakub Kicinski
2026-04-23 19:39 ` Jakub Kicinski
2026-04-23 19:56 ` David Howells
2026-04-23 19:59 ` David Howells
2026-04-23 21:46 ` Jakub Kicinski
2026-04-23 19:50 ` 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=177697381355.740120.3673972749152907468.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anderson@allelesecurity.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.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