CVE-2017-2618
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.5% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.5% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.5% · EPSS, next 30 days
- Weakness
- CWE-193
- Record status
- Modified
Affected
- Linux Kernel < 4.9.10
- Debian Linux 8.0
- Redhat Enterprise Linux 7.0
- Redhat Enterprise Linux Desktop 7.0
- Redhat Enterprise Linux Server 7.0
- Redhat Enterprise Linux Server Aus 7.3
- Redhat Enterprise Linux Server Aus 7.4
- Redhat Enterprise Linux Server Eus 7.3
Attack profile CVSS 3.0 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2017-2618.md and follow it. Check whether this project is affected by CVE-2017-2618. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2618
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0c461cb727d146c9ef2d3e86214f498b78b7d125
- https://marc.info/?l=selinux&m=148588165923772&w=2
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2618
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0c461cb727d146c9ef2d3e86214f498b78b7d125
- https://marc.info/?l=selinux&m=148588165923772&w=2
References
- http://www.securityfocus.com/bid/96272
- https://access.redhat.com/errata/RHSA-2017:0931
- https://access.redhat.com/errata/RHSA-2017:0932
- https://access.redhat.com/errata/RHSA-2017:0933
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2618
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0c461cb727d146c9ef2d3e86214f498b78b7d125
- https://marc.info/?l=selinux&m=148588165923772&w=2
- https://www.debian.org/security/2017/dsa-3791
- http://www.securityfocus.com/bid/96272
- https://access.redhat.com/errata/RHSA-2017:0931
- https://access.redhat.com/errata/RHSA-2017:0932
- https://access.redhat.com/errata/RHSA-2017:0933
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2618
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0c461cb727d146c9ef2d3e86214f498b78b7d125
- https://marc.info/?l=selinux&m=148588165923772&w=2
- https://www.debian.org/security/2017/dsa-3791