From: Simon Horman <horms@kernel.org>
To: Xiang Mei <xmei5@asu.edu>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
jakub@cloudflare.com, stable@vger.kernel.org,
co+0ea1ac045375cf05@bugs.sh
Subject: Re: [PATCH net] vlan: require the MAC header to be present in __vlan_insert_inner_tag()
Date: Sat, 19 Sep 2026 08:45:35 +0100 [thread overview]
Message-ID: <20260919074535.GW51261@horms.kernel.org> (raw)
In-Reply-To: <20260915083152.705309-1-xmei5@asu.edu>
On Tue, Sep 15, 2026 at 01:31:52AM -0700, Xiang Mei wrote:
> __vlan_insert_inner_tag() only guarantees head room via skb_cow_head(),
> never that mac_len bytes of MAC header are present. Its ETH_HLEN
> wrappers - __vlan_insert_tag() under skb_vlan_push(), and
> vlan_insert_tag() under validate_xmit_vlan() on the generic transmit
> path - therefore rewrite the first 16 bytes at skb->data: a 12-byte
> memmove plus two 2-byte stores at +12 and +14. No caller supplies the
> bound, while the pop helpers use skb_ensure_writable()/pskb_may_pull().
>
> An IFF_TUN device has hard_header_len == 0, so packet_snd() accepts a
> one-byte AF_PACKET/SOCK_RAW frame. The first vlan push only sets a
> hwaccel tag; the next - clsact "action vlan push" or
> bpf_skb_vlan_push() - enters the helper with skb->len still 1. The
> head comes from skbuff_small_head without __GFP_ZERO, so each push
> drags bytes from beyond skb->tail into the frame. After three the
> one-byte send leaves as 13 bytes carrying 11 bytes of uninitialised
> slab:
>
> 0000: 5a b3 62 12 80 88 ff ff 00 b3 62 12 81
> `------------------------------'
> only 0x5a was sent; the rest is slab, here the top 56 bits of a
> linear-map address
>
> Require the MAC header the helper rewrites to be present, so such a
> frame is dropped rather than transmitted.
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Cc: stable@vger.kernel.org
> Reported-by: co+0ea1ac045375cf05@bugs.sh
> Assisted-by: LLM
> Signed-off-by: Xiang Mei <xmei5@asu.edu>
> ---
> include/linux/if_vlan.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/include/linux/if_vlan.h b/include/linux/if_vlan.h
> index 20cc16ea4e5a..4846032bf4ff 100644
> --- a/include/linux/if_vlan.h
> +++ b/include/linux/if_vlan.h
> @@ -365,6 +365,9 @@ static inline int __vlan_insert_inner_tag(struct sk_buff *skb,
> const u8 meta_len = mac_len > ETH_TLEN ? skb_metadata_len(skb) : 0;
> struct vlan_ethhdr *veth;
>
> + if (unlikely(!pskb_may_pull(skb, mac_len)))
> + return -EINVAL;
> +
> if (skb_cow_head(skb, meta_len + VLAN_HLEN) < 0)
> return -ENOMEM;
TBH I am surprised that we have a bug like this in this function.
But your analysis matches my understanding of the code.
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2026-09-19 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 8:31 Xiang Mei
2026-09-19 7:45 ` Simon Horman [this message]
2026-09-19 22:49 ` Jakub Kicinski
2026-09-20 9:26 ` Simon Horman
2026-09-19 23:20 ` patchwork-bot+netdevbpf
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=20260919074535.GW51261@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bpf@vger.kernel.org \
--cc=co+0ea1ac045375cf05@bugs.sh \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jakub@cloudflare.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=xmei5@asu.edu \
/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®