From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Wenwen Wang <wang6495@umn.edu>
Cc: Kangjie Lu <kjlu@umn.edu>,
Andreas Noever <andreas.noever@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] thunderbolt: fix a missing-check bug
Date: Mon, 22 Oct 2018 11:05:26 +0300 [thread overview]
Message-ID: <20181022080526.GL2302@lahna.fi.intel.com> (raw)
In-Reply-To: <1540060698-17331-1-git-send-email-wang6495@umn.edu>
Hi,
On Sat, Oct 20, 2018 at 01:38:18PM -0500, Wenwen Wang wrote:
> In icm_copy(), the packet id 'hdr->packet_id' is firstly compared against
> 'req->npackets'. If it is less than 'req->npackets', the received packet.
> i.e., 'pkg->buffer', is then copied to 'req->response + offset' through
> memcpy(). It is worth noting that 'offset' is also calculated based on
> 'hdr->packet_id'. The problem here is that both the check and the
> calculation are conducted directly on 'pkg->buffer', which is actually a
> DMA memory region. Given that a device can also access the DMA region at
> any time, it is possible that a malicious device controlled by an attacker
> can modify the packet id after the check. By doing so, the attacker can
> supply comprised value into 'offset' and thus cause unexpected errors.
>
> This patch firstly copies the header of the packet and performs the check
> and the calculation on the copied version to fix the above issue. This
> patch also rewrites the header in 'req->response + offset' using the
> copied header to avoid a potential inconsistency issue.
Same comment here than with the previous one.
next prev parent reply other threads:[~2018-10-22 8:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 18:38 [PATCH] thunderbolt: fix a missing-check bug Wenwen Wang
2018-10-22 8:05 ` Mika Westerberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-20 20:15 Wenwen Wang
2018-10-22 8:06 ` Mika Westerberg
2018-10-20 19:47 Wenwen Wang
2018-10-22 8:05 ` Mika Westerberg
2018-10-20 17:55 [PATCH] thunderbolt: Fix " Wenwen Wang
2018-10-22 8:04 ` Mika Westerberg
2018-10-22 13:02 ` Wenwen Wang
2018-10-17 14:00 Wenwen Wang
2018-10-18 9:13 ` Mika Westerberg
2018-10-19 21:25 ` Wenwen Wang
2018-10-20 18:47 ` Yehezkel Bernat
2018-10-22 7:58 ` Mika Westerberg
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=20181022080526.GL2302@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=kjlu@umn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=wang6495@umn.edu \
/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