https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-02T21:56:08.915723+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2019-01419 bdu:2019-01419 2026-10-02T21:56:08.922039+00:00 bdu:2019-01419 https://cve.radiocsirt.org/vuln/euvd-2026-68578 EUVD-2026-68578 2026-10-02T21:56:08.922071+00:00 EUVD-2026-68578 https://cve.radiocsirt.org/vuln/fkie_cve-2018-17205 fkie_cve-2018-17205 2026-10-02T21:56:08.922085+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-vxv4-rrx9-5xfq GHSA-vxv4-rrx9-5xfq 2026-10-02T21:56:08.922119+00:00

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.

 https://cve.radiocsirt.org/vuln/gsd-2018-17205 gsd-2018-17205 2026-10-02T21:56:08.922168+00:00 gsd-2018-17205 https://cve.radiocsirt.org/vuln/rhsa-2018:3500 RHSA-2018:3500 — Red Hat Security Advisory: openvswitch security, bug fix, and enhancement update 2026-10-02T21:56:08.922189+00:00

openvswitch: Mishandle of group mods in lib/ofp-util.c:parse_group_prop_ntr_selection_method() allows for assertion failure openvswitch: Error during bundle commit in ofproto/ofproto.c:ofproto_rule_insert__() allows for crash openvswitch: Buffer over-read in lib/ofp-actions.c:decode_bundle()

 https://cve.radiocsirt.org/vuln/suse-su-2018:4128-1 SUSE-SU-2018:4128-1 — Security update for openvswitch 2026-10-02T21:56:08.922225+00:00

Security update for openvswitch

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-17205 UBUNTU-CVE-2018-17205 2026-10-02T21:56:08.922241+00:00

Affected: Ubuntu:18.04:LTS: openvswitch

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.