CVE-2018-18021
kernel: Privilege escalation on arm64 via KVM hypervisor
Overview
Description
arch/arm64/kvm/guest.c in KVM in the Linux kernel before 4.18.12 on the arm64 platform mishandles the KVM_SET_ON_REG ioctl. This is exploitable by attackers who can create virtual machines. An attacker can arbitrarily redirect the hypervisor flow of control (with full register control). An attacker can also cause a denial of service (hypervisor panic) via an illegal exception return. This occurs because of insufficient restrictions on userspace access to the core register file, and because PSTATE.M validation does not prevent unintended execution modes.
Source: OX vulnerability database
Severity
7.1 · HIGH
CVSS 3.0 base score, scored by NVD.
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Weakness: CWE-20
Affected packages · 0
No registry package. This ID affects operating system packages only.
Operating systems · 16 fixes
Oracle Linux 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 7 | kernel-uek +10 | 4.14.35-1818.4.5.el7uek |
Red Hat 1 release · 1 package
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| 7 | kernel +12 | 0:4.14.0-115.2.2.el7a | RHSA-2018:3656 |
debian 5 releases · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 11 | linux | 4.18.10-2 |
| 12 | linux | 4.18.10-2 |
| 13 | linux | 4.18.10-2 |
| 14 | linux | 4.18.10-2 |
| 9 | linux | 4.9.110-3+deb9u6 |
echo 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| linux | 4.18.10-2 |
root.io debian 3 releases · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 11 | rootio-linux | 4.18.10-2 |
| 12 | rootio-linux | 4.18.10-2 |
| 13 | rootio-linux | 4.18.10-2 |
ubuntu 2 releases · 3 packages
| Release | Package | Fixed in |
|---|---|---|
| 18.04 | linux-oracle | 4.15.0-1010.12 |
| 18.04 | linux-raspi2 | 4.15.0-1033.35 |
| 18.04 | linux | 4.15.0-47.50 |
| 18.04-ESM | linux-oracle | 4.15.0-1010.12 |
| 18.04-ESM | linux | 4.15.0-47.50 |
References
- git.kernel.org http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2a3f93459d689d990b3ecfbe782fec89b97d3279
- git.kernel.org http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d26c25a9d19b5976b319af528886f89cf455692d
- www.securityfocus.com http://www.securityfocus.com/bid/105550
- access.redhat.com https://access.redhat.com/errata/RHSA-2018:3656
- access.redhat.com https://access.redhat.com/security/cve/CVE-2018-18021
- cdn.kernel.org https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.18.12
- git.kernel.org https://git.kernel.org/linus/2a3f93459d689d990b3ecfbe782fec89b97d3279
- git.kernel.org https://git.kernel.org/linus/d26c25a9d19b5976b319af528886f89cf455692d
- github.com https://github.com/torvalds/linux/commit/2a3f93459d689d990b3ecfbe782fec89b97d3279
- github.com https://github.com/torvalds/linux/commit/d26c25a9d19b5976b319af528886f89cf455692d
Show all 24 references
- linux.oracle.com https://linux.oracle.com/cve/CVE-2018-18021.html
- linux.oracle.com https://linux.oracle.com/errata/ELSA-2018-4270.html
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2018-18021
- ubuntu.com https://ubuntu.com/security/notices/USN-3821-1
- ubuntu.com https://ubuntu.com/security/notices/USN-3821-2
- ubuntu.com https://ubuntu.com/security/notices/USN-3931-1
- ubuntu.com https://ubuntu.com/security/notices/USN-3931-2
- usn.ubuntu.com https://usn.ubuntu.com/3821-1/
- usn.ubuntu.com https://usn.ubuntu.com/3821-2/
- usn.ubuntu.com https://usn.ubuntu.com/3931-1/
- usn.ubuntu.com https://usn.ubuntu.com/3931-2/
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2018-18021
- www.debian.org https://www.debian.org/security/2018/dsa-4313
- www.openwall.com https://www.openwall.com/lists/oss-security/2018/10/02/2
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.