An issue was discovered in Open vSwitch (OvS) 2.7.x through 2.7.6, affecting ofproto_rule_insert__ in ofproto/ofproto.c. During bundle commit, flows that are added in a bundle are applied to ofproto in order. If a flow cannot be added (e.g., the flow action is a go-to for a group id that does not exist), OvS tries to revert back all previous flows that were successfully applied from the same bundle. This is possible since OvS maintains list of old flows that were replaced by flows from the bundle. While reinserting old flows, OvS has an assertion failure due to a check on rule state != RULE_INITIALIZED. This would work for new flows, but for an old flow the rule state is RULE_REMOVED. The assertion failure causes an OvS crash.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Centos_linux | — | Upgrade openvswitch-develUpgrade openvswitch-testUpgrade openvswitchUpgrade openvswitch-ovn-centralUpgrade openvswitch-ovn-commonUpgrade openvswitch-debuginfoUpgrade openvswitch-ovn-vtepUpgrade openvswitch-ovn-hostUpgrade python-openvswitch | Aug 28, 2019 | Sep 19, 2018 |
| Debian | — | Upgrade openvswitch | Jul 30, 2024 | Sep 19, 2018 |
| Redhat_linux | — | Upgrade openvswitch-ovn-centralUpgrade openvswitch-testUpgrade python-openvswitchUpgrade openvswitch-ovn-hostUpgrade openvswitch-ovn-vtepUpgrade openvswitch-develUpgrade openvswitchUpgrade openvswitch-debuginfoUpgrade openvswitch-ovn-common | Nov 6, 2018 | Sep 19, 2018 |
| Suse | — | Upgrade openvswitch | Dec 15, 2018 | Sep 19, 2018 |
| Ubuntu | — | Upgrade openvswitch-common | Feb 5, 2019 | Sep 19, 2018 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub