CVE-2013-4553
kernel: xen: lock order reversal between page_alloc_lock and mm_rwlock
Overview
Description
The XEN_DOMCTL_getmemlist hypercall in Xen 3.4.x through 4.3.x (possibly 4.3.1) does not always obtain the page_alloc_lock and mm_rwlock in the same order, which allows local guest administrators to cause a denial of service (host deadlock).
Source: OX vulnerability database
Severity
5.2 · MEDIUM
CVSS 2.0 base score, scored by NVD.
- Access vector
- Adjacent network
- Access complexity
- Medium
- Authentication
- Single
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:A/AC:M/Au:S/C:N/I:N/A:C
Weakness: CWE-119
Affected packages · 0
No registry package. This ID affects operating system packages only.
Operating systems · 6 fixes
debian 4 releases · 1 package
fixed 4
xen
| Release | Package | Fixed in |
|---|---|---|
| 11 | xen | 4.4.0-1 |
| 12 | xen | 4.4.0-1 |
| 13 | xen | 4.4.0-1 |
| 14 | xen | 4.4.0-1 |
echo 1 release · 1 package
fixed 1
xen
| Release | Package | Fixed in |
|---|---|---|
| xen | 4.4.0-1 |
openSUSE 1 release · 1 package
fixed 1
xen
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Tumbleweed | xen +6 | 4.7.0_12-1.3 | openSUSE-SU-2024:10196-1 |
References
- lists.opensuse.org http://lists.opensuse.org/opensuse-security-announce/2014-03/msg00010.html
- lists.opensuse.org http://lists.opensuse.org/opensuse-security-announce/2014-03/msg00021.html
- lists.opensuse.org http://lists.opensuse.org/opensuse-updates/2013-12/msg00059.html
- security.gentoo.org http://security.gentoo.org/glsa/glsa-201407-03.xml
- www.debian.org http://www.debian.org/security/2014/dsa-3006
- www.openwall.com http://www.openwall.com/lists/oss-security/2013/11/26/8
- access.redhat.com https://access.redhat.com/security/cve/CVE-2013-4553
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2013-4553
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2013-4553
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.