CVE-2025-1147: binutils: GNU Binutils nm nm.c internal_strlen buffer overflow | OX.Radar
Breaking: Ruby2Shell - Ruby Memory Corruption Flaws Expose Applications to Remote Code Execution
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2025-1147

binutils: GNU Binutils nm nm.c internal_strlen buffer overflow

Overview

Published
10 Feb 2025
Modified
17 Jun 2026
Low CVE
0 Registry packages
51 OS packages
12 Linux distributions
Yes Fix available

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

fixed 1
binutils
Azure Linux fixes for CVE-2025-1147
ReleasePackageFixed in
3.0 binutils 0:2.41-11.azl3

Red Hat 1 release · 1 package

affected 1
mingw-binutils
Red Hat fixes for CVE-2025-1147
ReleasePackageFixed in
9 mingw-binutils +3 affected

SUSE Linux Enterprise 5 releases · 4 packages

fixed 14
libucm-devel binutils perf bpftool
SUSE Linux Enterprise fixes for CVE-2025-1147
ReleasePackageFixed inAdvisory
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

fixed 1
binutils
SUSE Linux Enterprise Micro fixes for CVE-2025-1147
ReleasePackageFixed inAdvisory
6.2 binutils +2 2.45-160000.1.1 SUSE-SU-2025:21197-1

debian 4 releases · 1 package

affected 3 fixed 1
binutils
debian fixes for CVE-2025-1147
ReleasePackageFixed in
11 binutils affected
12 binutils affected
13 binutils affected
14 binutils 2.45-3

echo 1 release · 2 packages

fixed 2
binutils-gold binutils
echo fixes for CVE-2025-1147
ReleasePackageFixed in
binutils-gold 2.44-2+e1
binutils 2.45.50.20251125-1

openSUSE 1 release · 1 package

fixed 1
binutils
openSUSE fixes for CVE-2025-1147
ReleasePackageFixed inAdvisory
Tumbleweed binutils +5 2.45-1.2 openSUSE-SU-2025:15651-1

openSUSE Leap 1 release · 2 packages

fixed 2
binutils bpftool
openSUSE Leap fixes for CVE-2025-1147
ReleasePackageFixed inAdvisory
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

fixed 1
binutils
root.io debian fixes for CVE-2025-1147
ReleasePackageFixed in
12 binutils +1 2.40-2.root.io.19

root.io ubuntu 2 releases · 1 package

fixed 2
rootio-binutils
root.io ubuntu fixes for CVE-2025-1147
ReleasePackageFixed in
22.04 rootio-binutils 2.38-4ubuntu2.10
24.04 rootio-binutils 2.42-4ubuntu2.6

seal debian 1 release · 1 package

fixed 1
binutils
seal debian fixes for CVE-2025-1147
ReleasePackageFixed in
binutils +1 2.40-2+sp999

ubuntu 2 releases · 1 package

fixed 2
binutils
ubuntu fixes for CVE-2025-1147
ReleasePackageFixed in
22.04 binutils 2.38-4ubuntu2.10
24.04 binutils 2.42-4ubuntu2.6

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.