From: Dan Carpenter <dan.carpenter@oracle.com>
To: Suren Baghdasaryan <surenb@google.com>
Cc: security@kernel.org, kdeus@google.com,
Samuel Ortiz <sameo@linux.intel.com>,
"David S. Miller" <davem@davemloft.net>,
Allen Pais <allen.pais@oracle.com>,
Kees Cook <keescook@chromium.org>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] NFC: Fix possible memory corruption when handling SHDLC I-Frame commands
Date: Tue, 14 Aug 2018 12:54:13 +0300 [thread overview]
Message-ID: <20180814095413.vbjkcjkmytkffyaz@mwanda> (raw)
In-Reply-To: <20180813223910.26276-1-surenb@google.com>
Thanks. This is great. I'm so glad these are finally getting fixed.
Do we need to fix nfc_hci_msg_rx_work() and nfc_hci_recv_from_llc() as
well? In nfc_hci_recv_from_llc() we allow pipe to be NFC_HCI_FRAGMENT
(0x7f) so that's one element beyond the end of the array and the
NFC_HCI_HCP_RESPONSE isn't checked.
Also nci_hci_msg_rx_work() and nci_hci_data_received_cb() use
NCI_HCP_MSG_GET_PIPE() so those could be off by one.
regards,
dan carpenter
next prev parent reply other threads:[~2018-08-14 9:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 22:39 [PATCH 1/1] NFC: Fix possible memory corruption when handling SHDLC I-Frame commands Suren Baghdasaryan
2018-08-14 0:28 ` Kees Cook
2018-08-14 9:21 ` Greg KH
2018-08-14 9:54 ` Dan Carpenter [this message]
2018-08-14 16:57 ` Suren Baghdasaryan
2018-08-14 20:26 ` Suren Baghdasaryan
2018-08-14 20:33 ` Kees Cook
2018-08-14 20:55 ` Suren Baghdasaryan
2018-08-14 21:49 ` Kees Cook
2018-08-14 22:19 ` Suren Baghdasaryan
2018-08-14 22:38 ` Suren Baghdasaryan
2018-08-15 8:29 ` Dan Carpenter
2018-08-15 16:40 ` Suren Baghdasaryan
2018-08-17 12:06 ` Dan Carpenter
2018-08-17 14:47 ` Dan Carpenter
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=20180814095413.vbjkcjkmytkffyaz@mwanda \
--to=dan.carpenter@oracle.com \
--cc=allen.pais@oracle.com \
--cc=davem@davemloft.net \
--cc=kdeus@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=security@kernel.org \
--cc=surenb@google.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;
as well as URLs for NNTP newsgroup(s).