From: patchwork-bot+netdevbpf@kernel.org
To: Bryam Vargas <hexlabsecurity@proton.me>
Cc: wintera@linux.ibm.com, pabeni@redhat.com, kuba@kernel.org,
davem@davemloft.net, twinkler@linux.ibm.com, edumazet@google.com,
aswin@linux.ibm.com, netdev@vger.kernel.org, horms@kernel.org,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
hidayath@linux.ibm.com
Subject: Re: [PATCH net v3] net/iucv: fix the recvmsg window update
Date: Mon, 31 Aug 2026 23:00:05 +0000 [thread overview]
Message-ID: <178821720568.820683.16551074706319520837.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260828-b4-disp-33fac0ed-v3-1-e6d061880ee0@proton.me>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 28 Aug 2026 14:07:47 -0500 you wrote:
> From: Bryam Vargas <hexlabsecurity@proton.me>
>
> iucv_sock_recvmsg() sends the HiperSockets-only AF_IUCV_FLAG_WIN without
> testing the transport, so on a classic z/VM socket iucv_send_ctrl() sizes
> the skb through a NULL iucv->hs_dev. SO_MSGLIMIT accepts 1, so msglimit / 2
> is zero and one recvmsg() on its own socket is enough for an unprivileged
> process to take a spurious disconnect.
>
> [...]
Here is the summary with links:
- [net,v3] net/iucv: fix the recvmsg window update
https://git.kernel.org/netdev/net/c/fa5acd038ea6
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-31 23:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 19:07 [PATCH net v3] net/iucv: fix the recvmsg window update Bryam Vargas via B4 Relay
2026-08-31 15:08 ` Alexandra Winter
2026-08-31 22:52 ` Jakub Kicinski
2026-08-31 23: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=178821720568.820683.16551074706319520837.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aswin@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hexlabsecurity@proton.me \
--cc=hidayath@linux.ibm.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=twinkler@linux.ibm.com \
--cc=wintera@linux.ibm.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