Bug 1093076 (CVE-2014-3122)

Summary: CVE-2014-3122 Kernel: mm: try_to_unmap_cluster() should lock_page() before mlocking
Product: [Other] Security Response Reporter: Prasad Pandit <ppandit>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: agordeev, aquini, bhu, dhoward, esammons, fhrbata, gansalmon, iboverma, itamar, jforbes, jkacur, jkurik, jonathan, jross, jwboyer, kernel-maint, kernel-mgr, lgoncalv, lwang, madhu.chinakonda, matt, mchehab, mcressma, nobody, npajkovs, pholasek, plougher, pmatouse, rt-maint, rvrbovsk, williams
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
It was found that the try_to_unmap_cluster() function in the Linux kernel's Memory Managment subsystem did not properly handle page locking in certain cases, which could potentially trigger the BUG_ON() macro in the mlock_vma_page() function. A local, unprivileged user could use this flaw to crash the system.
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-10 07:27:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1078349, 1092365, 1093080, 1093081, 1093082, 1093083, 1093084    
Bug Blocks: 1092565    

Description Prasad Pandit 2014-04-30 14:36:10 UTC
Linux kernel kernel's Memory Management subsystem is vulnerable to a crash
caused by unlocked memory pages. It could occur during the memory page
migration or while cleaning the swap cache pages.

An unprivileged user/program could use this flaw to crash the system kernel,
resulting in DoS.

Upstream fix:
-------------
  -> https://git.kernel.org/linus/57e68e9cd65b4b8eb4045a1e0d0746458502554c

Comment 1 Prasad Pandit 2014-04-30 14:45:33 UTC
Statement:

This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5.

This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 6. Future kernel updates for Red Hat Enterprise Linux 6 may address this issue.

Comment 4 Prasad Pandit 2014-04-30 14:51:15 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1093084]

Comment 5 Fedora Update System 2014-05-10 03:21:07 UTC
kernel-3.14.3-200.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 6 Fedora Update System 2014-05-21 23:22:41 UTC
kernel-3.14.4-100.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 errata-xmlrpc 2014-05-27 16:28:13 UTC
This issue has been addressed in following products:

  MRG for RHEL-6 v.2

Via RHSA-2014:0557 https://rhn.redhat.com/errata/RHSA-2014-0557.html

Comment 8 Martin Prpič 2014-10-07 09:19:08 UTC
IssueDescription:

It was found that the try_to_unmap_cluster() function in the Linux kernel's Memory Managment subsystem did not properly handle page locking in certain cases, which could potentially trigger the BUG_ON() macro in the mlock_vma_page() function. A local, unprivileged user could use this flaw to crash the system.

Comment 9 errata-xmlrpc 2014-10-14 06:06:31 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6

Via RHSA-2014:1392 https://rhn.redhat.com/errata/RHSA-2014-1392.html