From: patchwork-bot+netdevbpf@kernel.org
To: Kees Cook <keescook@chromium.org>
Cc: krzysztof.kozlowski@linaro.org,
syzbot+210e196cef4711b65139@syzkaller.appspotmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linville@tuxdriver.com, ilane@ti.com,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] NFC: nci: Bounds check struct nfc_target arrays
Date: Tue, 06 Dec 2022 05:00:16 +0000 [thread overview]
Message-ID: <167030281674.5465.6825440514451542808.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221202214410.never.693-kees@kernel.org>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 2 Dec 2022 13:44:14 -0800 you wrote:
> While running under CONFIG_FORTIFY_SOURCE=y, syzkaller reported:
>
> memcpy: detected field-spanning write (size 129) of single field "target->sensf_res" at net/nfc/nci/ntf.c:260 (size 18)
>
> This appears to be a legitimate lack of bounds checking in
> nci_add_new_protocol(). Add the missing checks.
>
> [...]
Here is the summary with links:
- NFC: nci: Bounds check struct nfc_target arrays
https://git.kernel.org/netdev/net/c/e329e71013c9
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-12-06 5:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 21:44 [PATCH] NFC: nci: Bounds check struct nfc_target arrays Kees Cook
2022-12-05 8:17 ` Krzysztof Kozlowski
2022-12-06 5: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=167030281674.5465.6825440514451542808.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ilane@ti.com \
--cc=keescook@chromium.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+210e196cef4711b65139@syzkaller.appspotmail.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