CVE-2017-2618

UnknownEPSS 0.46%

Last modified

CVE-2017-2618 is a vulnerability of currently unknown severity. A flaw was found in the Linux kernel's handling of clearing SELinux attributes on /proc/pid/attr files before 4.9.10. An empty (null) write to this file can crash the system by causing the system to attempt to access unmapped kernel memory.. EPSS estimates a 0.46% chance of exploitation in the next 30 days.

Description

A flaw was found in the Linux kernel's handling of clearing SELinux attributes on /proc/pid/attr files before 4.9.10. An empty (null) write to this file can crash the system by causing the system to attempt to access unmapped kernel memory.

Metrics

EPSS Probability
0.46%

36.4th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
LinuxLinux Kernel< 4.9.10
DebianDebian Linux8.0
RedhatEnterprise Linux7.0
RedhatEnterprise Linux Desktop7.0
RedhatEnterprise Linux Server7.0
RedhatEnterprise Linux Server Aus7.3
RedhatEnterprise Linux Server Aus7.4
RedhatEnterprise Linux Server Eus7.3
RedhatEnterprise Linux Server Eus7.4
RedhatEnterprise Linux Server Eus7.5
RedhatEnterprise Linux Workstation7.0

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-2618?
A flaw was found in the Linux kernel's handling of clearing SELinux attributes on /proc/pid/attr files before 4.9.10. An empty (null) write to this file can crash the system by causing the system to attempt to access unmapped kernel memory.
How severe is CVE-2017-2618?
Severity scoring for CVE-2017-2618 is pending analysis. The EPSS model estimates a 0.46% probability of exploitation in the next 30 days.
How do I fix CVE-2017-2618?
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-2618?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST