Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1552849 - (CVE-2017-18221) CVE-2017-18221 kernel: Race condition in __munlock_pagevec function in mm/mlock.c
CVE-2017-18221 kernel: Race condition in __munlock_pagevec function in mm/mlo...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20180307,repor...
: Security
Depends On: 1553995 1552856
Blocks: 1552857
  Show dependency treegraph
 
Reported: 2018-03-07 15:53 EST by Pedro Sampaio
Modified: 2018-08-28 18:36 EDT (History)
44 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
The __munlock_pagevec function in mm/mlock.c in the Linux kernel, before 4.11.4, allows local users to cause a denial of service (NR_MLOCK accounting corruption) via crafted use of mlockall and munlockall system calls.
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Pedro Sampaio 2018-03-07 15:53:44 EST
The __munlock_pagevec function in mm/mlock.c in the Linux kernel before 4.11.4 allows local users to cause a denial of service (NR_MLOCK accounting corruption) via crafted use of mlockall and munlockall system calls.

References:

https://marc.info/?t=149567877900001&r=1&w=2

https://marc.info/?t=149569651900001&r=1&w=2

An upsteam patch:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=70feee0e1ef331b22cc51f383d532a0d043fbdcc
Comment 1 Pedro Sampaio 2018-03-07 15:57:26 EST
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1552856]
Comment 2 Justin M. Forbes 2018-03-07 17:58:33 EST
This was fixed for Fedora with the 4.11.4 stable updates.

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