Return-path: Received: from mail-lf0-f66.google.com ([209.85.215.66]:33127 "EHLO mail-lf0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754335AbeDWKCu (ORCPT ); Mon, 23 Apr 2018 06:02:50 -0400 Received: by mail-lf0-f66.google.com with SMTP id y15-v6so5916505lfj.0 for ; Mon, 23 Apr 2018 03:02:49 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20180423091631.GA14322@kroah.com> References: <1524045904-7005-1-git-send-email-amit.pundir@linaro.org> <1524045904-7005-5-git-send-email-amit.pundir@linaro.org> <20180423091631.GA14322@kroah.com> From: Amit Pundir Date: Mon, 23 Apr 2018 15:32:08 +0530 Message-ID: (sfid-20180423_120257_876239_FD2866D4) Subject: Re: [RESEND][PATCH 4/4] NFC: fdp: Fix possible buffer overflow in WCS4000 NFC driver To: Greg KH Cc: lkml , linux-wireless@vger.kernel.org, Samuel Ortiz , Christophe Ricard , Andy Shevchenko , John Stultz , Dmitry Shmidt , Todd Kjos , Android Kernel Team , Suren Baghdasaryan Content-Type: text/plain; charset="UTF-8" Sender: linux-wireless-owner@vger.kernel.org List-ID: On 23 April 2018 at 14:46, Greg KH wrote: > On Wed, Apr 18, 2018 at 03:35:04PM +0530, Amit Pundir wrote: >> From: Suren Baghdasaryan >> >> Possible buffer overflow when reading next_read_size bytes into >> tmp buffer after next_read_size was extracted from a previous packet. >> >> Signed-off-by: Suren Baghdasaryan >> Signed-off-by: Amit Pundir >> --- >> drivers/nfc/fdp/i2c.c | 10 ++++++++++ >> 1 file changed, 10 insertions(+) >> >> diff --git a/drivers/nfc/fdp/i2c.c b/drivers/nfc/fdp/i2c.c >> index c4da50e07bbc..08a4f82a2965 100644 >> --- a/drivers/nfc/fdp/i2c.c >> +++ b/drivers/nfc/fdp/i2c.c >> @@ -176,6 +176,16 @@ static int fdp_nci_i2c_read(struct fdp_i2c_phy *phy, struct sk_buff **skb) >> /* Packet that contains a length */ >> if (tmp[0] == 0 && tmp[1] == 0) { >> phy->next_read_size = (tmp[2] << 8) + tmp[3] + 3; >> + /* >> + * Ensure next_read_size does not exceed sizeof(tmp) >> + * for reading that many bytes during next iteration >> + */ >> + if (phy->next_read_size > FDP_NCI_I2C_MAX_PAYLOAD) { >> + dev_dbg(&client->dev, "%s: corrupted packet\n", >> + __func__); > > As Andy points out, no need for __func__ in any dev_dbg() call. Hi, Yes i'm working on v2 of this patch and on the comments I got on another patch in this series. Thanks, Amit Pundir > > thanks, > > greg k-h