Last Modified: Oct 13, 2026
Affected Product(s):
F5OS F5OS-A, F5OS-C
Known Affected Versions:
F5OS v2.0.0, F5OS v2.0.0-HR1, F5OS v2.0.0-HR2
Opened: Aug 20, 2026 Severity: 2-Critical
panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x... pc=0x...] goroutine ... [running]: github.com/flannel-io/flannel/pkg/backend/vxlan.(*network).watchVXLANDevice(...) .../pkg/backend/vxlan/vxlan_network.go:...
The k3s process terminates abruptly and is restarted by systemd.
While running F5OS-A 2.0.x on an rSeries appliance, the host experiences significant resource exhaustion, severe disk I/O latency, or temporary system stalls. During the stall, Netlink event delivery is delayed or disrupted while flannel's watchVXLANDevice() routine processes VXLAN network interface state changes.
There is no proactive workaround to prevent the crash under severe host stalls. The k3s daemon automatically restarts via systemd and recovers the VXLAN overlay.
None