Skip to content

Commit 9b51761

Browse files
committed
net: openvswitch: fix overwriting ct original tuple for ICMPv6
jira LE-3201 cve CVE-2024-38558 Rebuild_History Non-Buildable kernel-rt-4.18.0-553.22.1.rt7.363.el8_10 commit-author Ilya Maximets <i.maximets@ovn.org> commit 7c98817 OVS_PACKET_CMD_EXECUTE has 3 main attributes: - OVS_PACKET_ATTR_KEY - Packet metadata in a netlink format. - OVS_PACKET_ATTR_PACKET - Binary packet content. - OVS_PACKET_ATTR_ACTIONS - Actions to execute on the packet. OVS_PACKET_ATTR_KEY is parsed first to populate sw_flow_key structure with the metadata like conntrack state, input port, recirculation id, etc. Then the packet itself gets parsed to populate the rest of the keys from the packet headers. Whenever the packet parsing code starts parsing the ICMPv6 header, it first zeroes out fields in the key corresponding to Neighbor Discovery information even if it is not an ND packet. It is an 'ipv6.nd' field. However, the 'ipv6' is a union that shares the space between 'nd' and 'ct_orig' that holds the original tuple conntrack metadata parsed from the OVS_PACKET_ATTR_KEY. ND packets should not normally have conntrack state, so it's fine to share the space, but normal ICMPv6 Echo packets or maybe other types of ICMPv6 can have the state attached and it should not be overwritten. The issue results in all but the last 4 bytes of the destination address being wiped from the original conntrack tuple leading to incorrect packet matching and potentially executing wrong actions in case this packet recirculates within the datapath or goes back to userspace. ND fields should not be accessed in non-ND packets, so not clearing them should be fine. Executing memset() only for actual ND packets to avoid the issue. Initializing the whole thing before parsing is needed because ND packet may not contain all the options. The issue only affects the OVS_PACKET_CMD_EXECUTE path and doesn't affect packets entering OVS datapath from network interfaces, because in this case CT metadata is populated from skb after the packet is already parsed. Fixes: 9dd7f89 ("openvswitch: Add original direction conntrack tuple to sw_flow_key.") Reported-by: Antonin Bas <antonin.bas@broadcom.com> Closes: openvswitch/ovs-issues#327 Signed-off-by: Ilya Maximets <i.maximets@ovn.org> Acked-by: Aaron Conole <aconole@redhat.com> Acked-by: Eelco Chaudron <echaudro@redhat.com> Link: https://lore.kernel.org/r/20240509094228.1035477-1-i.maximets@ovn.org Signed-off-by: Jakub Kicinski <kuba@kernel.org> (cherry picked from commit 7c98817) Signed-off-by: Jonathan Maple <jmaple@ciq.com>
1 parent 4bb3978 commit 9b51761

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

net/openvswitch/flow.c

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -431,7 +431,6 @@ static int parse_icmpv6(struct sk_buff *skb, struct sw_flow_key *key,
431431
*/
432432
key->tp.src = htons(icmp->icmp6_type);
433433
key->tp.dst = htons(icmp->icmp6_code);
434-
memset(&key->ipv6.nd, 0, sizeof(key->ipv6.nd));
435434

436435
if (icmp->icmp6_code == 0 &&
437436
(icmp->icmp6_type == NDISC_NEIGHBOUR_SOLICITATION ||
@@ -440,6 +439,8 @@ static int parse_icmpv6(struct sk_buff *skb, struct sw_flow_key *key,
440439
struct nd_msg *nd;
441440
int offset;
442441

442+
memset(&key->ipv6.nd, 0, sizeof(key->ipv6.nd));
443+
443444
/* In order to process neighbor discovery options, we need the
444445
* entire packet.
445446
*/

0 commit comments

Comments
 (0)