Database/Firmware, BMC & network fabric

Arista EOS: IPsec tunnels re-established with stale SAs cause sequence mismatch and unstable traffic
Impact
On Arista platforms with hardware IPsec support and certain IPsec features enabled, a physical interface flap or an agent restart can bring a tunnel back up against already-existing Security Associations, leaving the two endpoints with mismatched sequence numbers and unstable communication across the tunnel. The practical effect for an operator is an encrypted link that silently stops carrying traffic reliably after an ordinary event - a link flap - with no configuration change to point at. Where IPsec carries inter-site or inter-datacenter traffic, that is storage replication and distributed training traffic degrading or dropping, and the trigger is something an attacker can often induce remotely by forcing a flap. Arista's record describes availability and confidentiality-of-session impact, not code execution.
Who can reach it
No authentication described; the condition is triggered by an interface flap or an agent restart on the affected switch, which an attacker able to influence the link - or any routine operational event - can cause. Only platforms with hardware IPsec support and the affected IPsec features enabled are exposed.
What to do
Apply the fixed EOS release or the hotfix listed in Arista security advisory 0134 for your platform. EOS upgrades reload the switch unless the advisory's hotfix path applies, so treat it as a per-device maintenance window on fabric or edge switches; check the advisory for whether a hitless hotfix is offered for your train. If you cannot patch soon, know that a tunnel showing this condition is recovered by clearing the stale SAs, and watch for flap-correlated tunnel instability.
References
Related entries
- NVIDIA DGX Spark firmware: out-of-bounds write reachable by a privileged local attackerCVE-2026-24262 · NVIDIA DGX Spark system firmwareHigh
- NVIDIA DGX Spark firmware: NULL pointer dereference reachable by a privileged local attackerCVE-2026-24263 · NVIDIA DGX Spark system firmwareHigh
- Linux kernel (drivers/net/ethernet/mellanox/mlx5/core/en): After a transmit-queue error triggers driver recovery, theCVE-2026-43466 · Linux kernel (drivers/net/ethernet/mellanox/mlx5/core/en)High
- OpenStack Ironic: send_raw step lets a deploy-capable user issue arbitrary IPMI commands to a nodeCVE-2026-54423 · OpenStack Ironic (IPMI management interface, send_raw clean/deploy step)High
- Insyde InsydeH2O (unverified firmware volume in the boot chain): Certain firmware volumes are executed without beingCVE-2026-6484 · Insyde InsydeH2O (unverified firmware volume in the boot chain)High
- InsydeH2O UEFI firmware: embedded UEFI Shell can be used to bypass Secure BootCVE-2026-6485 · InsydeH2O UEFI firmware (embedded UEFI Shell)High
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.