Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2015-3239: Off-by-one error in the dwarf_to_unw_regnum function in include/dwarf_i.h in libunwind 1.1 allows local users

27
Routine
LOW 3.3DOWNGRADE

CVE-2015-3239 is a low-severity flaw (CVSS 3.3) affecting libunwind. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Off-by-one error in the dwarf_to_unw_regnum function in include/dwarf_i.h in libunwind 1.1 allows local users to have unspecified impact via invalid dwarf opcodes.

Why this priority

  • Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score3.3 (Low)
EPSS exploit chance0.5% (top 57%)
CISA exploited listNo
WeaknessCWE-189
Published2015-08-26
Last modified2026-06-17
Publisher (CNA): Red Hat, Inc. · Vendor: libunwind project

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

libunwind project libunwind DOWNGRADE
Affected: 1.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.1
1. Check installed version
apt-cache policy libunwind || rpm -q libunwind || libunwind --version
2. No fixed release: DOWNGRADE to a release before 1.1 (Debian / Ubuntu)
apt-cache madison libunwind sudo apt install libunwind=<VERSION_BEFORE_1.1> sudo apt-mark hold libunwind
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list libunwind sudo dnf downgrade libunwind-<VERSION_BEFORE_1.1> sudo dnf versionlock add libunwind
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2015-3239?

libunwind: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2015-3239 being exploited?

CVE-2015-3239 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2015-3239 affect?

CVE-2015-3239 affects libunwind. Severity is low (CVSS 3.3). Off-by-one error in the dwarf_to_unw_regnum function in include/dwarf_i.h in libunwind 1.1 allows local users to have unspecified impact via invalid dwarf opcodes.

How urgent is CVE-2015-3239?

Priority 27/100. Public exploit reference

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.