oss-security - RE: CVE-2014-8159 kernel: infiniband: uverbs: unprotected physical memory access

Follow @Openwall on Twitter for new release announcements and other news

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Thu, 2 Apr 2015 07:52:17 +0000
From: Shachar Raindel <raindel@...lanox.com>
To: Roland Dreier <roland@...estorage.com>
CC: "oss-security@...ts.openwall.com" <oss-security@...ts.openwall.com>,
	"<linux-rdma@...r.kernel.org> (linux-rdma@...r.kernel.org)"
	<linux-rdma@...r.kernel.org>, "stable@...r.kernel.org"
	<stable@...r.kernel.org>
Subject: RE: CVE-2014-8159 kernel: infiniband: uverbs: unprotected physical
 memory access

> -----Original Message-----
> From: Roland Dreier [mailto:roland@...estorage.com]
> Sent: Wednesday, April 01, 2015 8:28 PM
> To: Shachar Raindel
> Cc: oss-security@...ts.openwall.com; <linux-rdma@...r.kernel.org>
> (linux-rdma@...r.kernel.org); stable@...r.kernel.org
> Subject: Re: CVE-2014-8159 kernel: infiniband: uverbs: unprotected
> physical memory access
> 
> On Wed, Mar 18, 2015 at 10:39 AM, Shachar Raindel <raindel@...lanox.com>
> wrote:
> > Date: Sun, 04 Jan 2015 18:30:32 +0200
> > Subject: [PATCH] IB/core: Prevent integer overflow in ib_umem_get
> address arithmetic
> 
> Just so we're clear, this bug has been known since January 4, and it's
> getting sent upstream now?
> 

This bug has been known since January, yes. To reduce the window of
vulnerability, we privately reported it to major distributions first,
aligning everyone on the same release date. Such synchronization takes
time. Given that the bug was not, to the best of our knowledge,
exploited in the wild, we believed that 3 months of embargo is not
exuberated. This is a common practice in the security industry, called
"responsible disclosure."

Following the kernel  security bugs policy [1], we reported it to 
the kernel security contacts few days before making the issue public.
Few days after issue became public, we published a clear report to all
of the relevant mailing lists.

> I assume we want it in 4.0 and -stable?

Yes. Should be applied ASAP to all kernels that contain uverbs.
We put some effort to make sure the patch will apply cleanly on all
historical versions of the kernel, so backporting should be simple.

Thanks,
--Shachar

[1] https://www.kernel.org/doc/Documentation/SecurityBugs

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.