From: Ilya Maximets <i.maximets@ovn.org>
To: Eelco Chaudron <echaudro@redhat.com>,
"Cen Zhang (Microsoft)" <blbllhy@gmail.com>
Cc: i.maximets@ovn.org, aconole@redhat.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org, dev@openvswitch.org,
linux-kernel@vger.kernel.org,
AutonomousCodeSecurity@microsoft.com,
tgopinath@linux.microsoft.com, kys@microsoft.com
Subject: Re: [PATCH net v3] net/openvswitch: check Ethernet header length in key_extract()
Date: Fri, 24 Jul 2026 14:34:54 +0200 [thread overview]
Message-ID: <efa2ca7b-ee6c-4758-832a-727c7c417c04@ovn.org> (raw)
In-Reply-To: <8082BACD-66E4-4C6C-ADA6-92231F1ECF39@redhat.com>
On 7/24/26 12:12 PM, Eelco Chaudron wrote:
>
>
> On 24 Jul 2026, at 1:37, Cen Zhang (Microsoft) wrote:
>
>> When a packet arrives on an ARPHRD_NONE device (e.g. TUN),
>> ovs_flow_key_extract() trusts the user-provided skb->protocol field: if
>> it is ETH_P_TEB, the packet is classified as MAC_PROTO_ETHERNET and
>> key_extract() is called without ensuring the skb has ETH_HLEN (14) bytes
>> of linear data. key_extract() unconditionally pulls 2 * ETH_ALEN bytes
>> for MAC addresses and parse_ethertype() pulls 2 more, either of which
>> triggers a kernel BUG in __skb_pull() when the linear area is too small.
>>
>> kernel BUG at include/linux/skbuff.h:2848!
>> RIP: 0010:key_extract+0xa7e/0xd90 net/openvswitch/flow.c:933
>> ovs_flow_key_extract+0x419/0xa70
>> ovs_vport_receive+0x222/0x390
>> netdev_frame_hook+0x3e0/0x630
>> tun_get_user+0x2d0c/0x38e0
>>
>> Fixed by adding checks in key_extract() before pulling the Ethernet
>> header.
>>
>> Fixes: 217ac77a3c25 ("openvswitch: allow L3 netdev ports")
>> Reported-by: AutonomousCodeSecurity@microsoft.com
>> Signed-off-by: Cen Zhang (Microsoft) <blbllhy@gmail.com>
>
> Hi Cen,
>
> Thanks for the new revision.
>
> The doc comment for key_extract() also needs updating. It currently
> states:
>
> * The caller must ensure that skb->len >= ETH_HLEN.
>
> The comment should be removed or replaced with a note that the
> function returns -EINVAL when the frame is too short to contain an
> Ethernet header.
>
> One more comment below.
>
> Cheers,
>
> Eelco
>
>> ---
>> v3: Use check_header() per review, fix format issue.
>> v2: Moved the check into key_extract() per Ilya Maximets.
>> Link: https://lore.kernel.org/all/20260721143602.64677-1-blbllhy@gmail.com
>>
>> net/openvswitch/flow.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/net/openvswitch/flow.c b/net/openvswitch/flow.c
>> index 66366982f604..fc4002353e17 100644
>> --- a/net/openvswitch/flow.c
>> +++ b/net/openvswitch/flow.c
>> @@ -911,6 +911,7 @@ static int key_extract_l3l4(struct sk_buff *skb, struct sw_flow_key *key)
>> static int key_extract(struct sk_buff *skb, struct sw_flow_key *key)
>> {
>> struct ethhdr *eth;
>> + int err;
>
> Since err is only used in the else block, it should be scoped there:
>
> } else {
> int err = check_header(skb, ETH_HLEN);
>
> if (unlikely(err))
> return err;
The 'eth' is also only used in the 'else' block, but defined at the top.
It doesn't matter where, but I think, we should keep them together.
>
>>
>> /* Flags are always used as part of stats */
>> key->tp.flags = 0;
>> @@ -926,6 +927,10 @@ static int key_extract(struct sk_buff *skb, struct sw_flow_key *key)
>> skb_reset_network_header(skb);
>> key->eth.type = skb->protocol;
>> } else {
>> + err = check_header(skb, ETH_HLEN);
>> + if (unlikely(err))
>> + return err;
>> +
>> eth = eth_hdr(skb);
>> ether_addr_copy(key->eth.src, eth->h_source);
>> ether_addr_copy(key->eth.dst, eth->h_dest);
>> --
>> 2.53.0
>
next prev parent reply other threads:[~2026-07-24 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 23:37 Cen Zhang (Microsoft)
2026-07-24 10:12 ` Eelco Chaudron
2026-07-24 12:34 ` Ilya Maximets [this message]
2026-07-25 4:34 ` Cen Zhang (Microsoft)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=efa2ca7b-ee6c-4758-832a-727c7c417c04@ovn.org \
--to=i.maximets@ovn.org \
--cc=AutonomousCodeSecurity@microsoft.com \
--cc=aconole@redhat.com \
--cc=blbllhy@gmail.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tgopinath@linux.microsoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®