CVE-2025-69649
Received Received - Intake

Null Pointer Dereference in GNU Binutils readelf Causes Crash

Publication date: 2026-03-06

Last updated on: 2026-03-11

Assigner: MITRE

Description
GNU Binutils thru 2.46 readelf contains a null pointer dereference vulnerability when processing a crafted ELF binary with malformed header fields. During relocation processing, an invalid or null section pointer may be passed into display_relocations(), resulting in a segmentation fault (SIGSEGV) and abrupt termination. No evidence of memory corruption beyond the null pointer dereference, nor any possibility of code execution, was observed.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-03-06
Last Modified
2026-03-11
Generated
2026-07-06
AI Q&A
2026-03-06
EPSS Evaluated
2026-07-05
NVD
CVE-2025-69649
EUVD
EUVD-2025-208345

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
gnu binutils to 2.46 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-476 The product dereferences a pointer that it expects to be valid but is NULL.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability exists in GNU Binutils through version 2.46, specifically in the readelf tool. It involves a null pointer dereference when processing a specially crafted ELF binary that has malformed header fields.

During the relocation processing phase, an invalid or null section pointer may be passed into the display_relocations() function, which causes a segmentation fault (SIGSEGV) and abrupt termination of the program.

There is no evidence that this vulnerability leads to memory corruption beyond the null pointer dereference, nor does it allow for code execution.

Impact Analysis

The primary impact of this vulnerability is that the readelf tool may crash unexpectedly when processing a maliciously crafted ELF binary.

This results in a denial of service condition where the tool terminates abruptly due to a segmentation fault.

Since there is no evidence of memory corruption or code execution, the risk of further exploitation is minimal.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

I don't know

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-69649. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart