CVE-2026-120221

frr: bgpd double free of peer-group Site-of-Origin when dynamic neighbors disconnect

Published Nov 13, 2026 CVSS 4.0 · 8.2 High EPSS n/a KEV · Not listed
Description
In FRRouting 8.4 and later, bgpd frees the same memory twice when dynamic BGP neighbors disconnect, if the peer-group used by a "bgp listen range" also has a Site-of-Origin configured ("neighbor PG soo"). Each dynamic neighbor shares the peer-group's SoO value instead of getting its own copy, but frees it as its own when the neighbor is deleted, which happens as soon as its connection closes. The first disconnect leaves the peer-group pointing at freed memory, and the second disconnect frees it again, causing bgpd to abort and drop all BGP sessions on the router. Any host whose address falls inside the listen range can trigger this by opening and closing two TCP connections to the BGP port, without sending any BGP message and without knowing the AS number, and can repeat it each time bgpd restarts. If the peer-group has a TCP-MD5 password, only hosts that know the password can trigger it. Two ordinary flaps of legitimate dynamic neighbors have the same effect. Between the two frees, displaying the configuration ("show running-config") or establishing a dynamic neighbor also reads the freed memory, which can crash bgpd after a single disconnect. Only configurations that combine a listen range with a SoO on the same peer-group are affected.

Analysis

No analysis available yet

Remediation

Vendor Workaround

Do not configure "neighbor <peer-group> soo" on a peer-group used by "bgp listen range". Instead, set the SoO extended community with an inbound route-map, or set "neighbor soo" on statically configured neighbors. Configuring a TCP-MD5 "password" on the peer-group limits the trigger to hosts that know the key.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description In FRRouting 8.4 and later, bgpd frees the same memory twice when dynamic BGP neighbors disconnect, if the peer-group used by a "bgp listen range" also has a Site-of-Origin configured ("neighbor PG soo"). Each dynamic neighbor shares the peer-group's SoO value instead of getting its own copy, but frees it as its own when the neighbor is deleted, which happens as soon as its connection closes. The first disconnect leaves the peer-group pointing at freed memory, and the second disconnect frees it again, causing bgpd to abort and drop all BGP sessions on the router. Any host whose address falls inside the listen range can trigger this by opening and closing two TCP connections to the BGP port, without sending any BGP message and without knowing the AS number, and can repeat it each time bgpd restarts. If the peer-group has a TCP-MD5 password, only hosts that know the password can trigger it. Two ordinary flaps of legitimate dynamic neighbors have the same effect. Between the two frees, displaying the configuration ("show running-config") or establishing a dynamic neighbor also reads the freed memory, which can crash bgpd after a single disconnect. Only configurations that combine a listen range with a SoO on the same peer-group are affected.
Title frr: bgpd double free of peer-group Site-of-Origin when dynamic neighbors disconnect
First Time appeared Frrouting
Frrouting frrouting
Weaknesses CWE-415
CWE-416
CPEs cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:*
Vendors & Products Frrouting
Frrouting frrouting
References
Metrics cvssV4_0

{'score': 8.2, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/AU:N/R:A'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
NetDEF
Published
Updated
Nov 13, 2026, 11:54 AM
Reserved
Oct 31, 2026, 6:17 PM
Status
Received
Published
Nov 13, 2026, 12:17 PM
Modified
Nov 13, 2026, 12:17 PM