From: zhudi <zhudi21@huawei.com>
To: <jgg@ziepe.ca>, <faisal.latif@intel.com>, <shiraz.saleem@intel.com>
Cc: <linux-rdma@vger.kernel.org>, <zhudi21@huawei.com>,
<rose.chen@huawei.com>
Subject: [PATCH] RDMA/i40iw: Fix a mmap handler exploitation
Date: Thu, 19 Nov 2020 17:35:23 +0800 [thread overview]
Message-ID: <20201119093523.7588-1-zhudi21@huawei.com> (raw)
From: Di Zhu <zhudi21@huawei.com>
Notice that i40iw_mmap() is used as mmap for file
/dev/infiniband/uverbs%d and these files have access mode
with 0666 specified by uverbs_devnode() and vma->vm_pgoff
is directly used to calculate pfn which is passed in
remap_pfn_range function without any valid validation.
This would result in a malicious process being able to pass an arbitrary
physical address to ‘mmap’ which would allow for access to all of
kernel memory from user space and eventually gain root privileges.
So, we should check whether final calculated value of vm_pgoff is
in range of specified pci resource before we use it to calculate
pfn which is passed in remap_pfn_range
Signed-off-by: Di Zhu <zhudi21@huawei.com>
---
drivers/infiniband/hw/i40iw/i40iw_verbs.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/infiniband/hw/i40iw/i40iw_verbs.c b/drivers/infiniband/hw/i40iw/i40iw_verbs.c
index 5ad381800f4d..7ec8f221eadb 100644
--- a/drivers/infiniband/hw/i40iw/i40iw_verbs.c
+++ b/drivers/infiniband/hw/i40iw/i40iw_verbs.c
@@ -185,6 +185,10 @@ static int i40iw_mmap(struct ib_ucontext *context, struct vm_area_struct *vma)
vma->vm_pgoff += db_addr_offset >> PAGE_SHIFT;
+ if (vma->vm_pgoff >
+ pci_resource_len(ucontext->iwdev->ldev->pcidev, 0) >> PAGE_SHIFT)
+ return -EINVAL;
+
if (vma->vm_pgoff == (db_addr_offset >> PAGE_SHIFT)) {
vma->vm_page_prot = pgprot_noncached(vma->vm_page_prot);
} else {
--
2.23.0
next reply other threads:[~2020-11-19 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 9:35 zhudi [this message]
2020-11-19 17:27 ` [PATCH] RDMA/i40iw: Fix a mmap handler exploitation Jason Gunthorpe
2020-11-20 23:56 ` Saleem, Shiraz
2020-11-21 0:18 ` Jason Gunthorpe
2020-11-21 2:45 ` Saleem, Shiraz
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=20201119093523.7588-1-zhudi21@huawei.com \
--to=zhudi21@huawei.com \
--cc=faisal.latif@intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=rose.chen@huawei.com \
--cc=shiraz.saleem@intel.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