A vulnerability was found in the bluetooth subsystem in the Linux kernel. This flaw takes affect while processing of incoming L2CAP commands - ConfigRequest, and ConfigResponse messages as uninitialized stack variables may be returned to an attacker in their uninitialized state. By manipulating the code flows that precede the handling of these configuration messages, an attacker can also gain some control over which data will be held in the uninitialized stack variables. This can allow him to bypass KASLR, and stack canaries protection - as both pointers and stack canaries may be leaked in this manner. This kind of flaw is considered an 'information leak' and can be used by attackers to defeat defensive protection mechanisms that would usually mitigate other flaws. References: http://seclists.org/oss-sec/2017/q4/357 An upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=06e7e776ca4d3654
Acknowledgments: Name: Armis Labs
Statement: This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. Future Linux kernel updates for the respective releases may address this issue.
Created kernel tracking bugs for this issue: Affects: fedora-all [bug 1522898]
What is Red Hat Enterprise Linux 7 for ARM 64, Red Hat Enterprise Linux 7 for Power 9 LE The kernel package as shipped with Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE is an updated kernel intended to support new architectures not available at the time of Red Hat Enterprise Linux 7 original shipping. The new kernel version is based on an upstream Linux kernel version 4.11. The offering is distributed with other updated packages, but most of the userspace is the standard Red Hat Enterprise Linux 7 Server RPM files. For more information please refer to: https://access.redhat.com/articles/3158541 https://access.redhat.com/articles/3158511
This was fixed with the 4.14.14 kernels for Fedora.
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2018:0654 https://access.redhat.com/errata/RHSA-2018:0654
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2018:0676 https://access.redhat.com/errata/RHSA-2018:0676
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2018:1062 https://access.redhat.com/errata/RHSA-2018:1062
This issue has been addressed in the following products: Red Hat Enterprise MRG 2 Via RHSA-2018:1170 https://access.redhat.com/errata/RHSA-2018:1170
This issue has been addressed in the following products: Red Hat Enterprise Linux 7.4 Extended Update Support Via RHSA-2018:1130 https://access.redhat.com/errata/RHSA-2018:1130
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Via RHSA-2018:1319 https://access.redhat.com/errata/RHSA-2018:1319