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
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.
Created kernel tracking bugs for this issue: Affects: fedora-all [bug 1093084]
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.
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.
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
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.
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