It was found that the Linux kernel's Infiniband subsystem did not properly sanitize input parameters while registering memory regions from the userspace via the (u)verbs API. As a result, an unrestricted physical memory access could be achieved. A local user with access to /dev/infiniband/uverbsX could use this flaw to crash the system or, potentially, escalate their privileges on the system.
Statement: This issue did affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, and 7, and Red Hat Enterprise MRG 2. This issue has been addressed in the respective releases.
Acknowledgements: Red Hat would like to thank Mellanox for reporting this issue.
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Via RHSA-2015:0674 https://rhn.redhat.com/errata/RHSA-2015-0674.html
Created kernel tracking bugs for this issue: Affects: fedora-all [bug 1200950]
This issue has been addressed in the following products: Red Hat Enterprise Linux 6.2 AUS Via RHSA-2015:0695 https://rhn.redhat.com/errata/RHSA-2015-0695.html
Any comments on rhel5, rhel7 fix? ...impact: important, public for more than a week now
Hello Peter. (In reply to Peter K from comment #10) > Any comments on rhel5, rhel7 fix? > ...impact: important, public for more than a week now This issue is currently planned to be be fixed in the upcoming Red Hat Enterprise Linux 5 and 7 regular kernel updates. If your use case requires this issue to be fixed earlier, please contact Red Hat Global Support Services (either through your TAM, or by logging into the Red Hat support website at http://www.redhat.com/support and filing a support ticket, or alternatively by phone at 1-888-RED-HAT1) and request a hotfix. Best regards, -- Petr Matousek / Red Hat Product Security
kernel-3.19.1-201.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
kernel-4.0.0-0.rc4.git0.1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2015:0727 https://rhn.redhat.com/errata/RHSA-2015-0727.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2015:0726 https://rhn.redhat.com/errata/RHSA-2015-0726.html
This issue has been addressed in the following products: MRG for RHEL-6 v.2 Via RHSA-2015:0751 https://rhn.redhat.com/errata/RHSA-2015-0751.html
kernel-3.19.3-100.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
This issue has been addressed in the following products: Red Hat Enterprise Linux 5 Via RHSA-2015:0783 https://rhn.redhat.com/errata/RHSA-2015-0783.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 6.5 EUS - Server and Compute Node Only Via RHSA-2015:0782 https://rhn.redhat.com/errata/RHSA-2015-0782.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 6.4 AUS - Server Only Via RHSA-2015:0803 https://rhn.redhat.com/errata/RHSA-2015-0803.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 5.9 EUS - Server Only Via RHSA-2015:0870 https://rhn.redhat.com/errata/RHSA-2015-0870.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 5.6 Long Life Via RHSA-2015:0919 https://rhn.redhat.com/errata/RHSA-2015-0919.html
Please clarify impact of above RHSA and EL6 kernel in relation to RHSA-2015-0674 / 504.16.2: [infiniband] core: Prevent integer overflow in ib_umem_get address arithmetic (Doug Ledford) [1181173 1179327] {CVE-2014-8159}
(In reply to Peter K from comment #25) > Please clarify impact of above RHSA and EL6 kernel in relation to > RHSA-2015-0674 / 504.16.2: > > [infiniband] core: Prevent integer overflow in ib_umem_get address > arithmetic (Doug Ledford) [1181173 1179327] {CVE-2014-8159} As you pointed out, CVE-2014-8159 was already addressed in Red Hat Enterprise Linux 6 via RHSA-2015:0674 and comment 24 is incorrect. I'm making the comment private so that it does not confuse other customers, copying it here: (In reply to errata-xmlrpc from comment #24) > This issue has been addressed in the following products: > > Red Hat Enterprise Linux 6 > > Via RHSA-2015:1081 https://rhn.redhat.com/errata/RHSA-2015-1081.html