Bug 1462153 (CVE-2017-1000370) - CVE-2017-1000370 kernel: offset2lib patch protection bypass
Summary: CVE-2017-1000370 kernel: offset2lib patch protection bypass
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2017-1000370
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1462828
Blocks: 1473653
TreeView+ depends on / blocked
 
Reported: 2017-06-16 10:37 UTC by Andrej Nemec
Modified: 2021-02-17 02:01 UTC (History)
37 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
The offset2lib patch as used in the i686 32-bit Linux kernel contains a vulnerability that allows a PIE binary to be execve()'ed with 1GB of arguments or environmental strings. the stack occupies the address 0x80000000 and the PIE binary is mapped above 0x40000000 nullifying the protection of the offset2lib patch.
Clone Of:
Environment:
Last Closed: 2019-06-08 03:15:00 UTC
Embargoed:

Attachments (Terms of Use)

Description Andrej Nemec 2017-06-16 10:37:46 UTC 
A flaw was found in the Linux kernel where execution of a PIE binary could allow for an attacker to corrupt memory or match priviledges of accessible setuid binaries on a system.

This is a different issue than  CVE-2017-1000371
Comment 1 Andrej Nemec 2017-06-16 10:37:57 UTC 
Acknowledgments:

Name: Qualys Inc
Comment 2 Andrej Nemec 2017-06-16 10:38:45 UTC 
External References:

https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt
Comment 3 Petr Matousek 2017-06-19 16:08:27 UTC 
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1462828]
Comment 6 Wade Mealing 2017-09-14 08:09:05 UTC 
Statement:

This issue does not affect the Linux kernel packages as shipped with Red Hat
Enterprise Linux 7 and MRG-2 as the i686 architecture is not supported by
this kernel.

This issue affects the Linux kernel packages as shipped with Red Hat
Enterprise Linux 5 and 6. At this time there is no plan to release an
update to fix this issue.
Note You need to log in before you can comment on or make changes to this bug.