Skip to content
Fencer Intel
medium 5.9

CVE-2015-8985 json

The pop_fail_stack function in the GNU C Library (aka glibc or libc6) allows context-dependent attackers to cause a denial of service (asse…

published 2017-03-20 9 y ago modified 2026-06-17 4 mo ago also EUVD-2015-8839

cvss
5.9
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.9%
EPSS 2.9% chance of exploitation in 30 days, percentile 87%
public exploits
0
none known

Summary

The pop_fail_stack function in the GNU C Library (aka glibc or libc6) allows context-dependent attackers to cause a denial of service (assertion failure and application crash) via vectors related to extended regular expression processing.

Patch / fix

  • gnu glibc 2.28
  • glibc Debian 14, Debian 13, Debian 12 2.28-1

debian advisories DEBIAN-CVE-2015-8985

  • glibc SLES 12 SP5, SLE Software Development Kit 12 SP5, OpenStack Cloud Crowbar 9 +4 more 2.22-114.22.1
  • glibc SLES for SAP 15 SP2, SLES for SAP 15 SP1, SLES for SAP 15 +18 more 2.26-13.65.1

suse advisories SUSE-SU-2022:3942-2SUSE-SU-2022:3942-1SUSE-SU-2022:0832-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-8985 updated cvss 1.9

glibc: potential denial of service in pop_fail_stack()

  • Red Hat Enterprise Linux 5 glibc Red Hat Enterprise Linux 6 nscd, glibc, glibc-utils, glibc-common
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 7 nscd, glibc, glibc-utils, glibc-common
    affected: no fix available

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

2.89% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-19 Data Processing Errors

References

Sources

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.