CVE-2013-4371 json
Use-after-free vulnerability in the libxl_list_cpupool function in the libxl toolstack library in Xen 4.2.x and 4.3.x, when running "under…
published 13y ago modified 4mo ago also EUVD-2013-4253
- cvss
- 4.4
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 34%
- public exploits
- 0
- none known
Summary
Use-after-free vulnerability in the libxl_list_cpupool function in the libxl toolstack library in Xen 4.2.x and 4.3.x, when running "under memory pressure," returns the original pointer when the realloc function fails, which allows local users to cause a denial of service (heap corruption and crash) and possibly execute arbitrary code via unspecified vectors.
Patch / fix
- xen Debian 14, Debian 13, Debian 12 4.4.0-1
debian advisories DEBIAN-CVE-2013-4371
Is CVE-2013-4371 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-4371 updated cvss 7.4
xen: use-after-free in libxl_list_cpupool under memory pressure (XSA-70)
-
Red Hat Enterprise Linux 5 kernel-xennot affected: vulnerable code not present
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.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.4 | AV:L/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-399 Resource Management Errors
References
-
security.gentoo.org
/glsa/glsa-201407-03.xml
vendor-advisory
-
openwall.com
/lists/oss-security/2013/10/10/12
mailing-list
Sources
- CVE List CVE-2013-4371
- NVD CVE-2013-4371
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.