From: patchwork-bot+netdevbpf@kernel.org
To: Haimin Zhang <tcs.kernel@gmail.com>
Cc: jmaloy@redhat.com, ying.xue@windriver.com, davem@davemloft.net,
kuba@kernel.org, netdev@vger.kernel.org,
tipc-discussion@lists.sourceforge.net, tcs_kernel@tencent.com
Subject: Re: [PATCH v2] net ticp:fix a kernel-infoleak in __tipc_sendmsg()
Date: Sat, 01 Jan 2022 02:50:09 +0000 [thread overview]
Message-ID: <164100540923.540.12070021072088953465.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1640918123-14547-1-git-send-email-tcs.kernel@gmail.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 31 Dec 2021 10:35:23 +0800 you wrote:
> From: Haimin Zhang <tcs_kernel@tencent.com>
>
> struct tipc_socket_addr.ref has a 4-byte hole,and __tipc_getname() currently
> copying it to user space,causing kernel-infoleak.
>
> BUG: KMSAN: kernel-infoleak in instrument_copy_to_user include/linux/instrumented.h:121 [inline]
> BUG: KMSAN: kernel-infoleak in instrument_copy_to_user include/linux/instrumented.h:121 [inline] lib/usercopy.c:33
> BUG: KMSAN: kernel-infoleak in _copy_to_user+0x1c9/0x270 lib/usercopy.c:33 lib/usercopy.c:33
> instrument_copy_to_user include/linux/instrumented.h:121 [inline]
> instrument_copy_to_user include/linux/instrumented.h:121 [inline] lib/usercopy.c:33
> _copy_to_user+0x1c9/0x270 lib/usercopy.c:33 lib/usercopy.c:33
> copy_to_user include/linux/uaccess.h:209 [inline]
> copy_to_user include/linux/uaccess.h:209 [inline] net/socket.c:287
> move_addr_to_user+0x3f6/0x600 net/socket.c:287 net/socket.c:287
> __sys_getpeername+0x470/0x6b0 net/socket.c:1987 net/socket.c:1987
> __do_sys_getpeername net/socket.c:1997 [inline]
> __se_sys_getpeername net/socket.c:1994 [inline]
> __do_sys_getpeername net/socket.c:1997 [inline] net/socket.c:1994
> __se_sys_getpeername net/socket.c:1994 [inline] net/socket.c:1994
> __x64_sys_getpeername+0xda/0x120 net/socket.c:1994 net/socket.c:1994
> do_syscall_x64 arch/x86/entry/common.c:51 [inline]
> do_syscall_x64 arch/x86/entry/common.c:51 [inline] arch/x86/entry/common.c:82
> do_syscall_64+0x54/0xd0 arch/x86/entry/common.c:82 arch/x86/entry/common.c:82
> entry_SYSCALL_64_after_hwframe+0x44/0xae
>
> [...]
Here is the summary with links:
- [v2] net ticp:fix a kernel-infoleak in __tipc_sendmsg()
https://git.kernel.org/netdev/net/c/d6d86830705f
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:[~2022-01-01 2:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 2:35 [PATCH v2] net ticp:fix a kernel-infoleak in __tipc_sendmsg() tcs.kernel
2022-01-01 2: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=164100540923.540.12070021072088953465.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=jmaloy@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tcs.kernel@gmail.com \
--cc=tcs_kernel@tencent.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.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;
as well as URLs for NNTP newsgroup(s).