CVE-2013-6885 json
The microcode on AMD 16h 00h through 0Fh processors does not properly handle the interaction between locked instructions and write-combined…
published 12y ago modified 4mo ago also EUVD-2013-6687
- cvss
- 4.7
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
The microcode on AMD 16h 00h through 0Fh processors does not properly handle the interaction between locked instructions and write-combined memory types, which allows local users to cause a denial of service (system hang) via a crafted application, aka the errata 793 issue.
Patch / fix
- linux Debian 14, Debian 13, Debian 12 3.14.2-1
debian advisories DEBIAN-CVE-2013-6885
- kernel RHEL 5 2.6.18-371.6.1.el5
- kernel-PAE RHEL 5 2.6.18-371.6.1.el5
- kernel-xen RHEL 5 2.6.18-371.6.1.el5
- kernel-kdump RHEL 5 2.6.18-371.6.1.el5
- kernel-debuginfo-common RHEL 5 2.6.18-371.6.1.el5
red hat advisories RHSA-2014:0285
Is CVE-2013-6885 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-6885 updated cvss 4.3
hw: AMD CPU erratum may cause core hang
-
Red Hat Enterprise Linux (v. 5 server) kernel 2.6.18-371.6.1.el5, kernel-PAE 2.6.18-371.6.1.el5, kernel-xen 2.6.18-371.6.1.el5, kernel-kdump 2.6.18-371.6.1.el5, kernel-debuginfo-common 2.6.18-371.6.1.el5 Red Hat Enterprise Linux Desktop (v. 5 client) kernel 2.6.18-371.6.1.el5, kernel-PAE 2.6.18-371.6.1.el5, kernel-xen 2.6.18-371.6.1.el5, kernel-kdump 2.6.18-371.6.1.el5, kernel-debuginfo-common 2.6.18-371.6.1.el5fixed: vendor fix RHSA-2014:0285
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.7 | AV:L/AC:M/Au:N/C:N/I:N/A:C |
Classification
- Weakness
-
- CWE-399 Resource Management Errors
References
-
lists.opensuse.org
/opensuse-security-announce/2014-04/msg00000.html
vendor-advisory
-
rhn.redhat.com
/errata/RHSA-2014-0285.html
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2014-03/msg00011.html
vendor-advisory
-
lists.fedoraproject.org
/pipermail/package-announce/2013-December/123553.html
vendor-advisory
-
lists.fedoraproject.org
/pipermail/package-announce/2013-December/124195.html
vendor-advisory
-
security.gentoo.org
/glsa/glsa-201407-03.xml
vendor-advisory
-
lists.fedoraproject.org
/pipermail/package-announce/2013-December/124199.html
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2014-03/msg00010.html
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2014-03/msg00026.html
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2014-03/msg00021.html
vendor-advisory
-
debian.org
/security/2015/dsa-3128
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2014-03/msg00015.html
vendor-advisory
-
openwall.com
/lists/oss-security/2013/12/02/1
mailing-list
- support.amd.com /TechDocs/51810_16h_00h-0Fh_Rev_Guide.pdf
- zdnet.com /blog/hardware/amd-owns-up-to-cpu-bug/18924
-
securityfocus.com
/bid/63983
vdb-entry
-
securitytracker.com
/id/1029415
vdb-entry
-
secunia.com
/advisories/55840
third-party-advisory
-
openwall.com
/lists/oss-security/2013/11/28/1
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/89335
vdb-entry
-
lists.dragonflybsd.org
/pipermail/kernel/2011-December/046594.html
mailing-list
- bugzilla.redhat.com /show_bug.cgi?id=1035823
Sources
- CVE List CVE-2013-6885
- NVD CVE-2013-6885
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.