FRRouting FRR up to 10.4.1 OSPF ospf_ext.c show_vty_unknown_tlv null pointer dereference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in FRRouting FRR up to 10.4.1. This issue affects the function show_vty_unknown_tlv of the file ospf_ext.c of the component OSPF Handler. This manipulation causes null pointer dereference.
This vulnerability is handled as CVE-2025-61104. There is not any exploit available.
Details
A vulnerability classified as problematic was found in FRRouting FRR up to 10.4.1. Affected by this vulnerability is the function show_vty_unknown_tlv of the file ospf_ext.c of the component OSPF Handler. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect availability. The summary by CVE is:
FRRouting/frr from v4.0 through v10.4.1 was discovered to contain a NULL pointer dereference via the show_vty_unknown_tlv function at ospf_ext.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted OSPF packet.
The advisory is shared at github.com. This vulnerability is known as CVE-2025-61104 since 09/26/2025. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 271925 (Linux Distros Unpatched Vulnerability : CVE-2025-61104), which helps to determine the existence of the flaw in a target environment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at Tenable (271925) and CERT Bund (WID-SEC-2025-2428). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Ubuntu Linux
- SUSE Linux
- SUSE openSUSE
- FRRouting Project FRRouting
Product
Vendor
Name
Version
Website
- Product: https://github.com/FRRouting/frr/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 271925
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-61104
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
09/26/2025 CVE reserved10/28/2025 Advisory disclosed
10/28/2025 VulDB entry created
02/27/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Not defined
CVE: CVE-2025-61104 (🔒)
GCVE (CVE): GCVE-0-2025-61104
GCVE (VulDB): GCVE-100-330301
CERT Bund: WID-SEC-2025-2428 - FRRouting (ospf_opaque.c): Mehrere Schwachstellen ermöglichen Denial of Service
Entry
Created: 10/28/2025 16:02Updated: 02/27/2026 21:27
Changes: 10/28/2025 16:02 (55), 10/29/2025 07:31 (2), 02/27/2026 21:27 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.