From: patchwork-bot+netdevbpf@kernel.org
To: Karsten Graul <kgraul@linux.ibm.com>
Cc: davem@davemloft.net, kuba@kernel.org, hca@linux.ibm.com,
raspl@linux.ibm.com, netdev@vger.kernel.org,
linux-s390@vger.kernel.org
Subject: Re: [PATCH net 0/2] net/smc: fix out of bound access in netlink interface
Date: Wed, 13 Jan 2021 04:30:08 +0000 [thread overview]
Message-ID: <161051220881.5581.17205976954559864201.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210112162122.26832-1-kgraul@linux.ibm.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Tue, 12 Jan 2021 17:21:20 +0100 you wrote:
> Please apply the following patch for smc to netdev's net tree.
>
> Both patches fix possible out-of-bounds reads. The original code expected
> that snprintf() reads len-1 bytes from source and appends the terminating
> null, but actually snprintf() first copies len bytes and finally overwrites
> the last byte with a null.
> Fix this by using memcpy() and terminating the string afterwards.
>
> [...]
Here is the summary with links:
- [net,1/2] smc: fix out of bound access in smc_nl_get_sys_info()
https://git.kernel.org/netdev/net/c/25fe2c9c4cd2
- [net,2/2] net/smc: use memcpy instead of snprintf to avoid out of bounds read
https://git.kernel.org/netdev/net/c/8a4465368964
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-01-13 4:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 16:21 [PATCH net 0/2] net/smc: fix out of bound access in netlink interface Karsten Graul
2021-01-12 16:21 ` [PATCH net 1/2] smc: fix out of bound access in smc_nl_get_sys_info() Karsten Graul
2021-01-12 16:21 ` [PATCH net 2/2] net/smc: use memcpy instead of snprintf to avoid out of bounds read Karsten Graul
2021-01-13 4:30 ` 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=161051220881.5581.17205976954559864201.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=hca@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=raspl@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