From: patchwork-bot+netdevbpf@kernel.org
To: Aswin Karuvally <aswin@linux.ibm.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, andrew+netdev@lunn.ch,
netdev@vger.kernel.org, linux-s390@vger.kernel.org,
hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com,
wintera@linux.ibm.com, borntraeger@linux.ibm.com,
svens@linux.ibm.com, horms@kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v2] s390/ctcm: Prevent XID null dereference
Date: Wed, 02 Sep 2026 00:36:45 +0000 [thread overview]
Message-ID: <178830940539.1844276.5420614099617158307.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260827063408.2168914-1-aswin@linux.ibm.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 27 Aug 2026 08:34:08 +0200 you wrote:
> The mpc_validate_xid() function sets grp->saved_xid2->xid2_flag2 to 0x40
> to signal XID validation error. If peer XID is NULL or r/w channel
> pairing mismatch happens, grp->saved_xid2 is never initialized. An
> attempt to set the flag in such case leads to NULL dereference.
>
> Fix this by using the always available priv->xid->xid2_flag2 instead of
> grp->saved_xid2->xid2_flag2 for validation errors.
>
> [...]
Here is the summary with links:
- [net,v2] s390/ctcm: Prevent XID null dereference
https://git.kernel.org/netdev/net/c/b264d8422779
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-09-02 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 6:34 [PATCH net v2] s390/ctcm: Prevent XID null dereference Aswin Karuvally
2026-08-28 6:34 ` sashiko-bot
2026-09-02 0:36 ` 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=178830940539.1844276.5420614099617158307.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=andrew+netdev@lunn.ch \
--cc=aswin@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=svens@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