From: Jeongjun Park <aha310510@gmail.com>
To: aha310510@gmail.com
Cc: alibuda@linux.alibaba.com, davem@davemloft.net,
dust.li@linux.alibaba.com, edumazet@google.com,
guwen@linux.alibaba.com, jaka@linux.ibm.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
tonylu@linux.alibaba.com, ubraun@linux.vnet.ibm.com,
utz.bacher@de.ibm.com, wenjia@linux.ibm.com,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: [PATCH net,v5,2/2] net/smc: modify smc_sock structure
Date: Tue, 20 Aug 2024 19:34:25 +0900 [thread overview]
Message-ID: <20240820103425.338094-1-aha310510@gmail.com> (raw)
In-Reply-To: <20240815043904.38959-1-aha310510@gmail.com>
Jeongjun Park wrote:
> Since inet_sk(sk)->pinet6 and smc_sk(sk)->clcsock practically
> point to the same address, when smc_create_clcsk() stores the newly
> created clcsock in smc_sk(sk)->clcsock, inet_sk(sk)->pinet6 is corrupted
> into clcsock. This causes NULL pointer dereference and various other
> memory corruptions.
>
> To solve this, we need to modify the smc_sock structure.
>
> Fixes: ac7138746e14 ("smc: establish new socket family")
> Signed-off-by: Jeongjun Park <aha310510@gmail.com>
Reported-by: syzkaller <syzkaller@googlegroups.com>
next prev parent reply other threads:[~2024-08-20 10:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 4:37 [PATCH net,v5,0/2] net/smc: prevent NULL pointer dereference in txopt_get Jeongjun Park
2024-08-15 4:38 ` [PATCH net,v5,1/2] net/smc: initialize ipv6_pinfo_offset in smc_inet6_prot and add smc6_sock structure Jeongjun Park
2024-08-20 10:31 ` Jeongjun Park
2024-08-15 4:39 ` [PATCH net,v5,2/2] net/smc: modify smc_sock structure Jeongjun Park
2024-08-20 10:34 ` Jeongjun Park [this message]
2024-08-20 10:45 ` Paolo Abeni
2024-08-20 11:02 ` Jeongjun Park
2024-08-21 5:41 ` Jan Karcher
2024-08-21 11:06 ` Jeongjun Park
2024-08-22 7:19 ` Jan Karcher
2024-08-26 2:56 ` D. Wythe
2024-08-26 19:24 ` Jan Karcher
2024-08-27 3:50 ` Jeongjun Park
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=20240820103425.338094-1-aha310510@gmail.com \
--to=aha310510@gmail.com \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=jaka@linux.ibm.com \
--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=syzkaller@googlegroups.com \
--cc=tonylu@linux.alibaba.com \
--cc=ubraun@linux.vnet.ibm.com \
--cc=utz.bacher@de.ibm.com \
--cc=wenjia@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