First published: Mon Nov 02 2015(Updated: )
It was found that a guest can DoS a host by triggering an infinite loop in microcode. If a guest in 32-bit mode enabled alignment exceptions, puts the exception handler in ring 3, and then triggers an alignment exception with an unaligned stack, then the microcode will enter an infinite loop. Because there's no instruction boundary the core never receives another interrupt (including SMIs). The host kernel panics pretty quickly due to the effects. A privileged user inside guest could use this flaw to crash the host kernel resulting in DoS. Upstream KVM patch: ------------------- -> <a href="http://permalink.gmane.org/gmane.linux.kernel/2082329">http://permalink.gmane.org/gmane.linux.kernel/2082329</a> References: ----------- -> <a href="http://www.openwall.com/lists/oss-security/2015/11/10/1">http://www.openwall.com/lists/oss-security/2015/11/10/1</a>
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/kernel | <0:2.6.32-573.12.1.el6 | 0:2.6.32-573.12.1.el6 |
redhat/kernel | <0:2.6.32-220.65.1.el6 | 0:2.6.32-220.65.1.el6 |
redhat/kernel | <0:2.6.32-358.69.1.el6 | 0:2.6.32-358.69.1.el6 |
redhat/kernel | <0:2.6.32-431.68.1.el6 | 0:2.6.32-431.68.1.el6 |
redhat/kernel | <0:2.6.32-504.40.1.el6 | 0:2.6.32-504.40.1.el6 |
redhat/kernel | <0:3.10.0-327.3.1.el7 | 0:3.10.0-327.3.1.el7 |
redhat/kernel | <0:3.10.0-229.24.2.el7 | 0:3.10.0-229.24.2.el7 |
Linux Kernel | <=4.2.3 | |
Xen xen-unstable | =4.3.0 | |
Xen xen-unstable | =4.3.1 | |
Xen xen-unstable | =4.3.2 | |
Xen xen-unstable | =4.3.3 | |
Xen xen-unstable | =4.3.4 | |
Xen xen-unstable | =4.4.0 | |
Xen xen-unstable | =4.4.1 | |
Xen xen-unstable | =4.4.2 | |
Xen xen-unstable | =4.4.3 | |
Xen xen-unstable | =4.4.4 | |
Xen xen-unstable | =4.5.0 | |
Xen xen-unstable | =4.5.1 | |
Xen xen-unstable | =4.5.2 | |
Xen xen-unstable | =4.5.3 | |
Xen xen-unstable | =4.5.5 | |
Xen xen-unstable | =4.6.0 | |
Xen xen-unstable | =4.6.1 | |
Xen xen-unstable | =4.6.2 | |
Xen xen-unstable | =4.6.3 | |
Xen xen-unstable | =4.6.4 | |
Xen xen-unstable | =4.6.5 | |
Xen xen-unstable | =4.6.6 | |
Oracle VM VirtualBox | >=4.0.0<=4.0.34 | |
Oracle VM VirtualBox | >=4.1.0<=4.1.42 | |
Oracle VM VirtualBox | >=4.2.0<=4.2.34 | |
Oracle VM VirtualBox | >=4.3.0<=4.3.29 | |
Oracle VM VirtualBox | >=5.0.0<=5.0.8 | |
Debian | =7.0 | |
Debian | =8.0 | |
Ubuntu | =12.04 | |
Ubuntu | =14.04 | |
Ubuntu | =15.10 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
CVE-2015-5307 is considered a high severity vulnerability due to its potential for a denial of service attack.
To fix CVE-2015-5307, you should upgrade to the kernel versions specified in the remedy section, such as 0:2.6.32-573.12.1.el6 or later.
CVE-2015-5307 affects various versions of Linux kernels, Xen hypervisors, and Oracle VM VirtualBox.
Yes, CVE-2015-5307 can be exploited by an attacker with access to the guest system, leading to denial of service on the host.
CVE-2015-5307 poses a threat of denial of service due to an infinite loop triggered in the microcode.