CVE-2025-1147
binutils: GNU Binutils nm nm.c internal_strlen buffer overflow
Overview
Description
A vulnerability has been found in GNU Binutils 2.43 and classified as problematic. Affected by this vulnerability is the function __sanitizer::internal_strlen of the file binutils/nm.c of the component nm. The manipulation of the argument const leads to buffer overflow. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used.
Source: OX vulnerability database
Severity
5.3 · LOW
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H
Weakness: CWE-119, CWE-120
Affected packages · 0
No registry package. This ID affects operating system packages only.
Operating systems · 32 fixes
Azure Linux 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 3.0 | binutils | 0:2.41-11.azl3 |
Red Hat 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 9 | mingw-binutils +3 | affected |
SUSE Linux Enterprise 5 releases · 4 packages
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| 15.4 | libucm-devel +8 | 1.11.1-150400.4.2.1 | SUSE-SU-2025:4096-1 |
| 15.4 | binutils +4 | 2.45-150100.7.57.1 | SUSE-SU-2025:4096-1 |
| 15.4 | perf +1 | 5.14.21-150400.44.20.1 | SUSE-SU-2025:4096-1 |
| 15.5 | libucm-devel +8 | 1.13.1-150500.4.2.5 | SUSE-SU-2025:4096-1 |
| 15.5 | binutils +4 | 2.45-150100.7.57.1 | SUSE-SU-2025:4096-1 |
| 15.5 | perf +1 | 5.14.21-150500.52.5.1 | SUSE-SU-2025:4096-1 |
8 more rows
SUSE Linux Enterprise Micro 1 release · 1 package
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| 6.2 | binutils +2 | 2.45-160000.1.1 | SUSE-SU-2025:21197-1 |
debian 4 releases · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 11 | binutils | affected |
| 12 | binutils | affected |
| 13 | binutils | affected |
| 14 | binutils | 2.45-3 |
echo 1 release · 2 packages
| Release | Package | Fixed in |
|---|---|---|
| binutils-gold | 2.44-2+e1 | |
| binutils | 2.45.50.20251125-1 |
openSUSE 1 release · 1 package
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Tumbleweed | binutils +5 | 2.45-1.2 | openSUSE-SU-2025:15651-1 |
openSUSE Leap 1 release · 2 packages
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| 16.0 | binutils +29 | 2.45-160000.1.1 | openSUSE-SU-2025:20150-1 |
| 16.0 | bpftool +1 | 7.5.0-160000.2.3 | openSUSE-SU-2025:20150-1 |
root.io debian 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 12 | binutils +1 | 2.40-2.root.io.19 |
root.io ubuntu 2 releases · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 22.04 | rootio-binutils | 2.38-4ubuntu2.10 |
| 24.04 | rootio-binutils | 2.42-4ubuntu2.6 |
seal debian 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| binutils +1 | 2.40-2+sp999 |
ubuntu 2 releases · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 22.04 | binutils | 2.38-4ubuntu2.10 |
| 24.04 | binutils | 2.42-4ubuntu2.6 |
References
- access.redhat.com https://access.redhat.com/security/cve/CVE-2025-1147
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2025-1147
- security.netapp.com https://security.netapp.com/advisory/ntap-20250404-0003/
- sourceware.org https://sourceware.org/bugzilla/attachment.cgi?id=15881
- sourceware.org https://sourceware.org/bugzilla/show_bug.cgi?id=32556
- sourceware.org https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=7be4186c22f89a87fff048c28910f5d26a0f61ce
- vuldb.com https://vuldb.com/?ctiid.295051
- vuldb.com https://vuldb.com/?id.295051
- vuldb.com https://vuldb.com/?submit.485254
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2025-1147
Show all 11 references
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.