Bug 1333830 (CVE-2015-3288) - CVE-2015-3288 kernel: zero page memory arbitrary modification
Summary: CVE-2015-3288 kernel: zero page memory arbitrary modification
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2015-3288
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: 1261582 1343127
Blocks: 1242013
TreeView+ depends on / blocked
 
Reported: 2016-05-06 13:49 UTC by Vladis Dronov
Modified: 2021-02-17 03:55 UTC (History)
35 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-06 14:02:46 UTC
Embargoed:


Attachments (Terms of Use)

Description Vladis Dronov 2016-05-06 13:49:56 UTC
A security flaw was found in the Linux kernel that
there is a way to arbitrary change zero page memory. Zero page is a page
which kernel maps into virtual address space on read page fault if the
page was not allocated before. Kernel has one zero page which used
everywhere. Programs that map 0 page are affected and code execution can
be gained. Upon running the exploit the system may become unusable as the
linker memory pages gets tainted. Furthermore, if the right code is put
in the 0 page, code execution is possible.

Comment 1 Vladis Dronov 2016-05-06 13:50:23 UTC
Acknowledgments:

Name: Kirill A. Shutemov (Intel)

Comment 3 Vladis Dronov 2016-05-06 13:55:24 UTC
Statement:

This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/.

This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue.


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