Bug 1519160 (CVE-2017-1000410) - CVE-2017-1000410 kernel: Stack information leak in the EFS element
Summary: CVE-2017-1000410 kernel: Stack information leak in the EFS element
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2017-1000410
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard: impact=moderate,public=20171206,repor...
Depends On: 1519626 1519627 1519628 1519629 1519630 1519631 1519632 1519633 1519634 1522898
Blocks: 1519163
TreeView+ depends on / blocked
 
Reported: 2017-11-30 10:26 UTC by Andrej Nemec
Modified: 2019-06-11 11:13 UTC (History)
46 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
A flaw was found in the processing of incoming L2CAP bluetooth commands. Uninitialized stack variables can be sent to an attacker leaking data in kernel address space.
Clone Of:
Environment:
Last Closed: 2019-06-08 03:32:31 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:0654 None None None 2018-04-10 05:06:57 UTC
Red Hat Product Errata RHSA-2018:0676 None None None 2018-04-10 08:10:52 UTC
Red Hat Product Errata RHSA-2018:1062 None None None 2018-04-10 09:33:52 UTC
Red Hat Product Errata RHSA-2018:1130 None None None 2018-04-17 16:21:38 UTC
Red Hat Product Errata RHSA-2018:1170 None None None 2018-04-17 15:30:55 UTC
Red Hat Product Errata RHSA-2018:1319 None None None 2018-05-08 18:59:27 UTC

Description Andrej Nemec 2017-11-30 10:26:13 UTC
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

Comment 1 Andrej Nemec 2017-11-30 10:26:27 UTC
Acknowledgments:

Name: Armis Labs

Comment 3 Wade Mealing 2017-12-01 04:41:03 UTC
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.

Comment 7 Adam Mariš 2017-12-06 17:17:23 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1522898]

Comment 9 Vladis Dronov 2018-01-21 21:06:56 UTC
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

Comment 10 Justin M. Forbes 2018-01-22 15:15:10 UTC
This was fixed with the 4.14.14 kernels for Fedora.

Comment 11 errata-xmlrpc 2018-04-10 05:06:36 UTC
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

Comment 12 errata-xmlrpc 2018-04-10 08:10:32 UTC
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

Comment 13 errata-xmlrpc 2018-04-10 09:33:29 UTC
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

Comment 14 errata-xmlrpc 2018-04-17 15:30:32 UTC
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

Comment 15 errata-xmlrpc 2018-04-17 16:21:16 UTC
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

Comment 16 errata-xmlrpc 2018-05-08 18:59:08 UTC
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


Note You need to log in before you can comment on or make changes to this bug.