net: openvswitch: fix skb leak on flow key update failure during ct
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ec0d043d05e6e3c0c2fac5de922c800c027c6386 · < e0ba8eaef2a0d02a7a485e6a7157e47272b65cea| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: openvswitch: fix skb leak on flow key update failure during ct
ovs_ct_execute() always steals or frees the skb on failure while ovs_flow_key_update() does not. So, if it fails and we return right away, the skb ends up leaked.
Fix that by breaking instead and letting the common error handling code at the bottom of the loop to free the skb properly.
This is a very unlikely scenario as it requires the packet to become unparseable by applying a set of actions on a previously parseable skb, but should be fixed nevertheless.
Reported by Sashiko.
From the CVE record · Linux
The Linux kernel’s Open vSwitch connection-tracking path can leak a packet buffer when a flow key update fails. This rare failure requires a set of actions to make a previously parseable packet unparseable. The input does not specify whether an attacker can trigger it or what access would be required.
Operators running Linux kernels that use Open vSwitch should check their kernel versions; affected versions are not specified.