Netdev List
 help / color / mirror / Atom feed
From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Weiming Shi <bestswngs@gmail.com>,
	Florian Fainelli <florian.fainelli@broadcom.com>,
	Jonas Gorski <jonas.gorski@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>, Vladimir Oltean <olteanv@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Álvaro Fernández Rojas" <noltari@gmail.com>,
	"Xiang Mei" <xmei5@asu.edu>,
	co+28eef7d8af9428e6@bugs.sh, stable@vger.kernel.org
Subject: Re: [PATCH net] net: dsa: tag_brcm: legacy FCS: request needed tailroom
Date: Tue, 8 Sep 2026 10:09:03 -0700	[thread overview]
Message-ID: <70bcc9af-5003-4131-94d9-2c7f23506124@broadcom.com> (raw)
In-Reply-To: <20260908165047.2786340-1-bestswngs@gmail.com>

On 9/8/26 09:50, Weiming Shi wrote:
> The legacy FCS tagger calculates the CRC over skb->len bytes starting at
> skb->data. When a nonlinear skb reaches the tagger, this reads past the
> linear head into unrelated slab memory.
> 
> The tagger appends an Ethernet FCS but does not declare that tailroom. As a
> result, DSA leaves NETIF_F_SG and NETIF_F_FRAGLIST enabled on the user
> port, and nonlinear skbs can reach the CRC calculation.
> 
> Declare the required tailroom. DSA will then clear those features and the
> networking core will linearize skbs before the tagger runs.
> 
> A KASAN-enabled dsa_loop test using this tagger reports:
> 
>    BUG: KASAN: slab-out-of-bounds in crc32_le
>    Read of size 1 at addr ffff8880397086c0 by task exp/135
> 
>    Call Trace:
>     crc32_le (lib/crc/crc32-main.c:38)
>     brcm_leg_fcs_tag_xmit (net/dsa/tag_brcm.c:343)
>     dsa_user_xmit (net/dsa/user.c:942)
>     dev_hard_start_xmit (net/core/dev.c:3937)
>     __dev_queue_xmit (net/core/dev.c:4926)
>     packet_sendmsg (net/packet/af_packet.c:3110)
>     __sys_sendto (net/socket.c:2281)
> 
>    The buggy address belongs to the object at ffff888039708400
>     which belongs to the cache skbuff_small_head of size 704
>    The buggy address is located 0 bytes to the right of
>     allocated 704-byte region [ffff888039708400, ffff8880397086c0)
> 
> Fixes: ef07df397a62 ("net: dsa: tag_brcm: add support for legacy FCS tags")
> Cc: stable@vger.kernel.org
> Reported-by: co+28eef7d8af9428e6@bugs.sh
> Closes: https://lore.kernel.org/all/jH6u350kaBRuqklDjd3k3BW4nWzp0tYRjq3p%40bugs.sh/
> Assisted-by: Claude:gpt-5
> Signed-off-by: Weiming Shi <bestswngs@gmail.com>

Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
-- 
Florian


  reply	other threads:[~2026-09-08 17:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 16:50 [PATCH net] net: dsa: tag_brcm: legacy FCS: request needed tailroom Weiming Shi
2026-09-08 17:09 ` Florian Fainelli [this message]
2026-09-09 20:40 ` 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=70bcc9af-5003-4131-94d9-2c7f23506124@broadcom.com \
    --to=florian.fainelli@broadcom.com \
    --cc=andrew@lunn.ch \
    --cc=bestswngs@gmail.com \
    --cc=co+28eef7d8af9428e6@bugs.sh \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jonas.gorski@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=noltari@gmail.com \
    --cc=olteanv@gmail.com \
    --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