Release bionic does not exist.
Bugs fixes in "frr"
| Origin | Bug number | Title | Date fixed |
|---|---|---|---|
| CVE | CVE-2025-61102 | FRRouting/frr from v4.0 through v10.4.1 was discovered to contain a NULL pointer dereference via the show_vty_ext_link_adj_sid function at ospf_ext.c | 2026-02-17 |
| CVE | CVE-2025-61101 | FRRouting/frr from v4.0 through v10.4.1 was discovered to contain a NULL pointer dereference via the show_vty_ext_link_rmt_itf_addr function at ospf_ | 2026-02-17 |
| CVE | CVE-2025-61100 | FRRouting/frr from v2.0 through v10.4.1 was discovered to contain a NULL pointer dereference via the ospf_opaque_lsa_dump function at ospf_opaque.c. | 2026-02-17 |
| CVE | CVE-2025-61099 | FRRouting/frr from v2.0 through v10.4.1 was discovered to contain a NULL pointer dereference via the opaque_info_detail function at ospf_opaque.c. Th | 2026-02-17 |
| Launchpad | 2113448 | FRR forgets learned MACs on redundant EVPN over VXLAN links | 2026-02-03 |
| Launchpad | 2113448 | FRR forgets learned MACs on redundant EVPN over VXLAN links | 2026-02-03 |
| Launchpad | 2113448 | FRR forgets learned MACs on redundant EVPN over VXLAN links | 2025-10-21 |
| Launchpad | 2113448 | FRR forgets learned MACs on redundant EVPN over VXLAN links | 2025-10-21 |
| CVE | CVE-2024-55553 | In FRRouting (FRR) before 10.3 from 6.0 onward, all routes are re-validated if the total size of an update received via RTR exceeds the internal sock | 2025-01-27 |
| CVE | CVE-2024-55553 | In FRRouting (FRR) before 10.3 from 6.0 onward, all routes are re-validated if the total size of an update received via RTR exceeds the internal sock | 2025-01-27 |
| CVE | CVE-2024-55553 | In FRRouting (FRR) before 10.3 from 6.0 onward, all routes are re-validated if the total size of an update received via RTR exceeds the internal sock | 2025-01-27 |
| CVE | CVE-2024-55553 | In FRRouting (FRR) before 10.3 from 6.0 onward, all routes are re-validated if the total size of an update received via RTR exceeds the internal sock | 2025-01-27 |
| CVE | CVE-2024-55553 | In FRRouting (FRR) before 10.3 from 6.0 onward, all routes are re-validated if the total size of an update received via RTR exceeds the internal sock | 2025-01-27 |
| CVE | CVE-2024-55553 | In FRRouting (FRR) before 10.3 from 6.0 onward, all routes are re-validated if the total size of an update received via RTR exceeds the internal sock | 2025-01-27 |
| CVE | CVE-2024-55553 | In FRRouting (FRR) before 10.3 from 6.0 onward, all routes are re-validated if the total size of an update received via RTR exceeds the internal sock | 2025-01-27 |
| CVE | CVE-2024-55553 | In FRRouting (FRR) before 10.3 from 6.0 onward, all routes are re-validated if the total size of an update received via RTR exceeds the internal sock | 2025-01-27 |
| CVE | CVE-2024-44070 | An issue was discovered in FRRouting (FRR) through 10.1. bgp_attr_encap in bgpd/bgp_attr.c does not check the actual remaining stream length before t | 2024-09-17 |
| CVE | CVE-2024-44070 | An issue was discovered in FRRouting (FRR) through 10.1. bgp_attr_encap in bgpd/bgp_attr.c does not check the actual remaining stream length before t | 2024-09-17 |
| CVE | CVE-2024-44070 | An issue was discovered in FRRouting (FRR) through 10.1. bgp_attr_encap in bgpd/bgp_attr.c does not check the actual remaining stream length before t | 2024-09-17 |
| CVE | CVE-2024-44070 | An issue was discovered in FRRouting (FRR) through 10.1. bgp_attr_encap in bgpd/bgp_attr.c does not check the actual remaining stream length before t | 2024-09-17 |
About
-
Send Feedback to @ubuntu_updates
