From: "Pablo Vallespín Aranguren" <pablopva014@gmail.com>
To: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"open list:TULIP NETWORK DRIVERS" <netdev@vger.kernel.org>,
"open list:TULIP NETWORK DRIVERS" <linux-parisc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Cc: Greg KH <gregkh@linuxfoundation.org>
Subject: [PATCH] net: tulip: xircom_cb: drop runt frames before skb copy
Date: Fri, 31 Jul 2026 20:33:34 +0200 [thread overview]
Message-ID: <amzqfjeo0Yo1p0Rd@ThinkPad-P15> (raw)
investigate_read_descriptor() takes the 11-bit packet length straight
from the device-written descriptor and subtracts 4 for the CRC. A
length below 4 underflows pkt_len to a negative value, which is then
passed to skb_put_data() as a huge unsigned length and corrupts memory
past the end of the freshly allocated skb.
Drop the frame as a length error if pkt_len is negative after CRC
removal.
Signed-off-by: Pablo Vallespín Aranguren <pablopva014@gmail.com>
Assisted-by: gkh_clanker_t1000
---
drivers/net/ethernet/dec/tulip/xircom_cb.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/drivers/net/ethernet/dec/tulip/xircom_cb.c b/drivers/net/ethernet/dec/tulip/xircom_cb.c
index e5d2ede13845..62c64da1c8fa 100644
--- a/drivers/net/ethernet/dec/tulip/xircom_cb.c
+++ b/drivers/net/ethernet/dec/tulip/xircom_cb.c
@@ -1110,6 +1110,11 @@ investigate_read_descriptor(struct net_device *dev, struct xircom_private *card,
/* minus 4, we don't want the CRC */
struct sk_buff *skb;
+ if (pkt_len < 0) {
+ dev->stats.rx_length_errors++;
+ goto out;
+ }
+
if (pkt_len > 1518) {
netdev_err(dev, "Packet length %i is bogus\n", pkt_len);
pkt_len = 1518;
--
2.55.0
next reply other threads:[~2026-07-31 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 18:33 Pablo Vallespín Aranguren [this message]
2026-07-31 19:26 ` [PATCH] net: tulip: xircom_cb: drop runt frames before skb copy David Laight
2026-07-31 20:56 ` Pablo Vallespín Aranguren
2026-07-31 23:55 ` Jakub Kicinski
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=amzqfjeo0Yo1p0Rd@ThinkPad-P15 \
--to=pablopva014@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.