CVE-2017-18221
UnknownEPSS 0.50%
Last modified
CVE-2017-18221 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.50% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | < 4.11.4 |
References
- http://www.securityfocus.com/bid/103321Third Party Advisory, VDB Entry
- https://github.com/torvalds/linux/commit/70feee0e1ef331b22cc51f383d532a0d043fbdccPatch, Third Party Advisory
- https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.11.4Release Notes, Vendor Advisory
- http://www.securityfocus.com/bid/103321Third Party Advisory, VDB Entry
- https://github.com/torvalds/linux/commit/70feee0e1ef331b22cc51f383d532a0d043fbdccPatch, Third Party Advisory
- https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.11.4Release Notes, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-18221?
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.
How severe is CVE-2017-18221?
Severity scoring for CVE-2017-18221 is pending analysis. The EPSS model estimates a 0.50% probability of exploitation in the next 30 days.
How do I fix CVE-2017-18221?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2017-18221?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
