Skip to main content

Blog post · November 19, 2026 · aviznetworks.com

Aviz Networks outlines RiskControl for mitigating SONiC CVEs

Summary

Aviz Networks outlines RiskControl, a SONiC approach that pairs Aviz Network Copilot CVE assessment with Tetragon eBPF runtime controls deployed via Aviz ONES. The approach lets network teams limit exposure from newly disclosed vulnerabilities without rushing upgrades on production switches.

Assessment and exposure

The article describes a widening gap between vulnerability disclosure and exploitation, with AI-assisted research said to shorten the time to a working exploit from months to days. Upgrading production switches typically takes weeks or months because of validation, change windows, and rollback planning. The company argues that faster patching alone cannot close this exposure window.

Aviz Network Copilot is presented as an agentic platform customers can use to build their own CVE assessment workflow. It correlates a CVE against inventory, software versions, and configuration to show exposure, affected devices and services, and mitigation paths with suggested maintenance windows.

Runtime mitigation with Tetragon

Tetragon is described as an open source eBPF-based security and observability engine that observes and enforces policy at the kernel level. Policies load dynamically without a reboot or traffic disruption, and eBPF programs are verified before they run. Because SONiC runs on the Linux kernel, the article states that Tetragon covers the host and every SONiC container, including Aviz Certified Community SONiC and other distributions.

The company states that Tetragon will be enabled by default in the upcoming Aviz CCS 2.0 release. Aviz also plans to embed Tetragon agents in its regular CCS releases and provide lifecycle and control management through ONES. The article stresses that Tetragon is a mitigating policy and not a replacement for patching.

Example policy for CVE-2026-46331

The article cites CVE-2026-46331, a Linux kernel vulnerability in the act_pedit traffic-control module that can corrupt cached data and potentially lead to elevated privileges or a system crash. The example policy blocks loading of the act_pedit module through a kernel module request hook, so the vulnerable code is not activated. The article notes that the vulnerability remains in the code while services continue running and the switch keeps forwarding traffic.

Staged deployment and fleet management

The article recommends a staged workflow that begins with observe-only monitoring, moves to enforcement after validation, and ends with retiring the control after a permanent patch or upgrade. Aviz ONES is described as providing one place to deploy, monitor, enforce, roll back, and retire policies across devices, sites, and multivendor environments.

This Blog Summary is a fact-based summary of the vendor blog. For enterprise network and security leaders, the post presents runtime mitigation as a way to manage CVE exposure while upgrades remain under validation.

Our summary. The original keeps its own byline.

Read the original on aviznetworks.com

Companies in this article

Topics