public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Karsten Graul <kgraul@linux.ibm.com>
To: David Miller <davem@davemloft.net>, Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, linux-s390@vger.kernel.org,
	Heiko Carstens <hca@linux.ibm.com>,
	alibuda@linux.alibaba.com
Subject: [PATCH net 0/3] net/smc: fixes 2022-04-08
Date: Fri,  8 Apr 2022 17:10:32 +0200	[thread overview]
Message-ID: <20220408151035.1044701-1-kgraul@linux.ibm.com> (raw)

Please apply the following patches to netdev's net tree.

Patch 1 fixes two usages of snprintf() with non null-terminated
string which results into an out-of-bounds read.
Pach 2 fixes a syzbot finding where a pointer check was missed
before the call to dev_name().
Patch 3 fixes a crash when already released memory is used as
a function pointer.

Karsten Graul (3):
  net/smc: use memcpy instead of snprintf to avoid out of bounds read
  net/smc: Fix NULL pointer dereference in smc_pnet_find_ib()
  net/smc: Fix af_ops of child socket pointing to released memory

 net/smc/af_smc.c   | 14 ++++++++++++--
 net/smc/smc_clc.c  |  6 ++++--
 net/smc/smc_pnet.c |  5 +++--
 3 files changed, 19 insertions(+), 6 deletions(-)

-- 
2.32.0


             reply	other threads:[~2022-04-08 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 15:10 Karsten Graul [this message]
2022-04-08 15:10 ` [PATCH net 1/3] net/smc: use memcpy instead of snprintf to avoid out of bounds read Karsten Graul
2022-04-08 15:10 ` [PATCH net 2/3] net/smc: Fix NULL pointer dereference in smc_pnet_find_ib() Karsten Graul
2022-04-08 15:10 ` [PATCH net 3/3] net/smc: Fix af_ops of child socket pointing to released memory Karsten Graul
2022-04-11  8:38   ` D. Wythe
2022-04-12  1:40 ` [PATCH net 0/3] net/smc: fixes 2022-04-08 patchwork-bot+netdevbpf

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=20220408151035.1044701-1-kgraul@linux.ibm.com \
    --to=kgraul@linux.ibm.com \
    --cc=alibuda@linux.alibaba.com \
    --cc=davem@davemloft.net \
    --cc=hca@linux.ibm.com \
    --cc=kuba@kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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