First published: Fri Apr 12 2013(Updated: )
Xen 4.2.x, 4.1.x, and earlier, when the hypervisor is running "under memory pressure" and the Xen Security Module (XSM) is enabled, uses the wrong ordering of operations when extending the per-domain event channel tracking table, which causes a use-after-free and allows local guest kernels to inject arbitrary events and gain privileges via unspecified vectors.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Xen xen-unstable | =3.0.2 | |
Xen xen-unstable | =3.0.3 | |
Xen xen-unstable | =3.0.4 | |
Xen xen-unstable | =3.1.3 | |
Xen xen-unstable | =3.1.4 | |
Xen xen-unstable | =3.2.0 | |
Xen xen-unstable | =3.2.1 | |
Xen xen-unstable | =3.2.2 | |
Xen xen-unstable | =3.2.3 | |
Xen xen-unstable | =3.3.0 | |
Xen xen-unstable | =3.3.1 | |
Xen xen-unstable | =3.3.2 | |
Xen xen-unstable | =3.4.0 | |
Xen xen-unstable | =3.4.1 | |
Xen xen-unstable | =3.4.2 | |
Xen xen-unstable | =3.4.3 | |
Xen xen-unstable | =3.4.4 | |
Xen xen-unstable | =4.0.0 | |
Xen xen-unstable | =4.0.1 | |
Xen xen-unstable | =4.0.2 | |
Xen xen-unstable | =4.0.3 | |
Xen xen-unstable | =4.0.4 | |
Xen xen-unstable | =4.1.0 | |
Xen xen-unstable | =4.1.1 | |
Xen xen-unstable | =4.1.2 | |
Xen xen-unstable | =4.1.3 | |
Xen xen-unstable | =4.1.4 | |
Xen xen-unstable | =4.2.0 | |
Xen xen-unstable | =4.2.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-1920 has a medium severity level due to its potential to allow local guest kernels to inject malicious code.
Fixing CVE-2013-1920 involves updating the Xen hypervisor to a version that is patched against the vulnerability.
CVE-2013-1920 affects Xen versions 4.2.x, 4.1.x, and earlier, including versions down to 3.0.2.
CVE-2013-1920 cannot be exploited remotely, as it requires local access to the affected guest kernel.
CVE-2013-1920 can lead to unauthorized access and privilege escalation if exploited by a local attacker.