All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Szycik <marcin.szycik@linux.intel.com>
To: Bui Quang Minh <minhquangbui99@gmail.com>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Paul M Stillwell Jr <paul.m.stillwell.jr@intel.com>,
	Rasesh Mody <rmody@marvell.com>,
	Sudarsana Kalluru <skalluru@marvell.com>,
	GR-Linux-NIC-Dev@marvell.com,
	Krishna Gudipati <kgudipat@brocade.com>,
	Anil Gurumurthy <anil.gurumurthy@qlogic.com>,
	Sudarsana Kalluru <sudarsana.kalluru@qlogic.com>,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Fabian Frederick <fabf@skynet.be>,
	Saurav Kashyap <skashyap@marvell.com>,
	Javed Hasan <jhasan@marvell.com>,
	GR-QLogic-Storage-Upstream@marvell.com,
	Nilesh Javali <nilesh.javali@cavium.com>,
	Arun Easi <arun.easi@cavium.com>,
	Manish Rangankar <manish.rangankar@cavium.com>,
	Vineeth Vijayan <vneethv@linux.ibm.com>,
	Peter Oberparleiter <oberpar@linux.ibm.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	Sven Schnelle <svens@linux.ibm.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-s390@vger.kernel.org, linux-scsi@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	intel-wired-lan@lists.osuosl.org,
	Saurav Kashyap <saurav.kashyap@cavium.com>
Subject: Re: [Intel-wired-lan] [PATCH 0/5] Ensure the copied buf is NULL terminated
Date: Tue, 23 Apr 2024 13:10:16 +0200	[thread overview]
Message-ID: <eb54c7bb-db63-4361-b42f-dc02e2c37fbf@linux.intel.com> (raw)
In-Reply-To: <20240422-fix-oob-read-v1-0-e02854c30174@gmail.com>



On 22.04.2024 18:41, Bui Quang Minh wrote:
> Hi everyone,
> 
> I found that some drivers contains an out-of-bound read pattern like this
> 
> 	kern_buf = memdup_user(user_buf, count);
> 	...
> 	sscanf(kern_buf, ...);
> 
> The sscanf can be replaced by some other string-related functions. This
> pattern can lead to out-of-bound read of kern_buf in string-related
> functions.
> 
> This series fix the above issue by replacing memdup_user with
> memdup_user_nul or allocating count + 1 buffer then writing the NULL
> terminator to end of buffer after userspace copying.
> 
> Thanks,
> Quang Minh.
> 
> Signed-off-by: Bui Quang Minh <minhquangbui99@gmail.com>
> ---
> Bui Quang Minh (5):
>       drivers/net/ethernet/intel-ice: ensure the copied buf is NULL terminated
>       drivers/net/brocade-bnad: ensure the copied buf is NULL terminated
>       drivers/scsi/bfa/bfad: ensure the copied buf is NULL terminated
>       drivers/scsi/qedf: ensure the copied buf is NULL terminated
>       drivers/s390/cio: ensure the copied buf is NULL terminated

Typically you don't include path to module in title, instead:
ice: ensure the copied buf is NULL terminated
bna: ensure the copied buf is NULL terminated
etc.

> 
>  drivers/net/ethernet/brocade/bna/bnad_debugfs.c | 4 ++--
>  drivers/net/ethernet/intel/ice/ice_debugfs.c    | 8 ++++----
>  drivers/s390/cio/cio_inject.c                   | 3 ++-
>  drivers/scsi/bfa/bfad_debugfs.c                 | 4 ++--
>  drivers/scsi/qedf/qedf_debugfs.c                | 2 +-
>  5 files changed, 11 insertions(+), 10 deletions(-)
> ---
> base-commit: ed30a4a51bb196781c8058073ea720133a65596f
> change-id: 20240422-fix-oob-read-19ae7f8f3711
> 
> Best regards,

Thanks,
Marcin

  parent reply	other threads:[~2024-04-23 11:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 16:41 [Intel-wired-lan] [PATCH 0/5] Ensure the copied buf is NULL terminated Bui Quang Minh
2024-04-22 16:41 ` Bui Quang Minh
2024-04-22 16:41 ` [Intel-wired-lan] [PATCH 1/5] drivers/net/ethernet/intel-ice: ensure " Bui Quang Minh
2024-04-22 16:41   ` Bui Quang Minh
2024-04-23  9:20   ` [Intel-wired-lan] " Przemek Kitszel
2024-04-23  9:20     ` Przemek Kitszel
2024-04-22 16:41 ` [Intel-wired-lan] [PATCH 2/5] drivers/net/brocade-bnad: " Bui Quang Minh
2024-04-22 16:41   ` Bui Quang Minh
2024-04-22 16:41 ` [Intel-wired-lan] [PATCH 3/5] drivers/scsi/bfa/bfad: " Bui Quang Minh
2024-04-22 16:41   ` Bui Quang Minh
2024-04-22 16:41 ` [Intel-wired-lan] [PATCH 4/5] drivers/scsi/qedf: " Bui Quang Minh
2024-04-22 16:41   ` Bui Quang Minh
2024-04-22 16:41 ` [Intel-wired-lan] [PATCH 5/5] drivers/s390/cio: " Bui Quang Minh
2024-04-22 16:41   ` Bui Quang Minh
2024-04-23  6:50   ` [Intel-wired-lan] " Heiko Carstens
2024-04-23  6:50     ` Heiko Carstens
2024-04-23 14:46     ` [Intel-wired-lan] " Bui Quang Minh
2024-04-23 14:46       ` Bui Quang Minh
2024-04-24 11:55       ` [Intel-wired-lan] " Heiko Carstens
2024-04-24 11:55         ` Heiko Carstens
2024-04-23 11:10 ` Marcin Szycik [this message]
2024-04-23 11:25   ` [Intel-wired-lan] [PATCH 0/5] Ensure " Przemek Kitszel
2024-04-23 11:25     ` Przemek Kitszel

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=eb54c7bb-db63-4361-b42f-dc02e2c37fbf@linux.intel.com \
    --to=marcin.szycik@linux.intel.com \
    --cc=GR-Linux-NIC-Dev@marvell.com \
    --cc=GR-QLogic-Storage-Upstream@marvell.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=agordeev@linux.ibm.com \
    --cc=anil.gurumurthy@qlogic.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=arun.easi@cavium.com \
    --cc=axboe@kernel.dk \
    --cc=borntraeger@linux.ibm.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fabf@skynet.be \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=jhasan@marvell.com \
    --cc=kgudipat@brocade.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=manish.rangankar@cavium.com \
    --cc=martin.petersen@oracle.com \
    --cc=minhquangbui99@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nilesh.javali@cavium.com \
    --cc=oberpar@linux.ibm.com \
    --cc=pabeni@redhat.com \
    --cc=paul.m.stillwell.jr@intel.com \
    --cc=rmody@marvell.com \
    --cc=saurav.kashyap@cavium.com \
    --cc=skalluru@marvell.com \
    --cc=skashyap@marvell.com \
    --cc=sudarsana.kalluru@qlogic.com \
    --cc=svens@linux.ibm.com \
    --cc=vneethv@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.