From: patchwork-bot+netdevbpf@kernel.org
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: davem@davemloft.net, kuba@kernel.org, linville@tuxdriver.com,
sameo@linux.intel.com, linux-nfc@lists.01.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
thadeu.cascardo@canonical.com, stable@vger.kernel.org,
syzbot+80fb126e7f7d8b1a5914@syzkaller.appspotmail.com,
butterflyhuangxx@gmail.com
Subject: Re: [RESEND PATCH] nfc: fix NULL ptr dereference in llcp_sock_getname() after failed connect
Date: Tue, 01 Jun 2021 05:50:03 +0000 [thread overview]
Message-ID: <162252660360.4642.10005433752607898965.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210531072138.5219-1-krzysztof.kozlowski@canonical.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Mon, 31 May 2021 09:21:38 +0200 you wrote:
> It's possible to trigger NULL pointer dereference by local unprivileged
> user, when calling getsockname() after failed bind() (e.g. the bind
> fails because LLCP_SAP_MAX used as SAP):
>
> BUG: kernel NULL pointer dereference, address: 0000000000000000
> CPU: 1 PID: 426 Comm: llcp_sock_getna Not tainted 5.13.0-rc2-next-20210521+ #9
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-1 04/01/2014
> Call Trace:
> llcp_sock_getname+0xb1/0xe0
> __sys_getpeername+0x95/0xc0
> ? lockdep_hardirqs_on_prepare+0xd5/0x180
> ? syscall_enter_from_user_mode+0x1c/0x40
> __x64_sys_getpeername+0x11/0x20
> do_syscall_64+0x36/0x70
> entry_SYSCALL_64_after_hwframe+0x44/0xae
>
> [...]
Here is the summary with links:
- [RESEND] nfc: fix NULL ptr dereference in llcp_sock_getname() after failed connect
https://git.kernel.org/netdev/net/c/4ac06a1e013c
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:[~2021-06-01 5:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 7:21 Krzysztof Kozlowski
2021-06-01 5: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=162252660360.4642.10005433752607898965.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=butterflyhuangxx@gmail.com \
--cc=davem@davemloft.net \
--cc=krzysztof.kozlowski@canonical.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfc@lists.01.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+80fb126e7f7d8b1a5914@syzkaller.appspotmail.com \
--cc=thadeu.cascardo@canonical.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
all inboxes | Powered by JetHome®