CVE-2025-61100: Null Pointer Dereference
Published Oct 27, 2025
·Updated
FRRouting/frr from v2.0 through v10.4.1 was discovered to contain a NULL pointer dereference via the ospfopaquelsadump function at ospfopaque.c. This vulnerability allows attackers to cause a Denial of Service (DoS) under specific malformed LSA conditions.
Affected Software
8 affected componentsFixes available
Frrouting FRR>=2.0<=10.4.1
Frrouting FRRouting>=2.0<=10.4.1
Microsoft cbl2 frr 8.5.5-3
Microsoft azl3 frr 9.1.1-3
Microsoft cbl2 frr 8.5.5-5
Microsoft cbl2 frr 8.5.5-4
Microsoft azl3 frr 9.1.1-5
Microsoft azl3 frr 9.1.1-4
Remediation
Event History
Oct 27, 2025
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·07:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Nov 2, 2025
Data Sourced
via Microsoft·01:02 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·01:02 AM
Affected Software
Updated
via Microsoft·09:02 AM
DescriptionSeverity
Updated
via Microsoft·09:02 AM
Affected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-61100?
CVE-2025-61100 has been classified as a Denial of Service vulnerability.
2
How do I fix CVE-2025-61100?
To fix CVE-2025-61100, upgrade FRRouting frr to version 10.4.2 or later.
3
What versions of FRRouting are affected by CVE-2025-61100?
CVE-2025-61100 affects FRRouting frr versions from 2.0 up to and including 10.4.1.
4
What type of attack can CVE-2025-61100 facilitate?
CVE-2025-61100 can be exploited to cause a Denial of Service under specific malformed LSA conditions.
5
Who is responsible for the vulnerable software related to CVE-2025-61100?
FRRouting is the responsible party for the vulnerable software identified in CVE-2025-61100.