From: Ping-Ke Shih <pkshih@realtek.com>
To: Jiaxin Li <18135327133@163.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH v3 1/1] wifi: rtl8180: reject RX frames longer than MAX_RX_SIZE
Date: Thu, 22 Oct 2026 02:49:54 +0000 [thread overview]
Message-ID: <59bba0199d1a435f983d76a550929898@realtek.com> (raw)
In-Reply-To: <20261021135906.1493-2-18135327133@163.com>
Jiaxin Li <18135327133@163.com> wrote:
> rtl8180_handle_rx() passes the 12-bit length field from the RX
> descriptor to skb_put() without clamping it to MAX_RX_SIZE. The skb was
> allocated with dev_alloc_skb(MAX_RX_SIZE), so a descriptor length above
> MAX_RX_SIZE extends the skb past its allocated tailroom.
>
> Store the reported length in a local variable and drop the frame before
> allocating the replacement RX skb when it exceeds MAX_RX_SIZE.
>
> Signed-off-by: Jiaxin Li <18135327133@163.com>
Reviewed-by: Ping-Ke Shih <pkshih@realtek.com>
prev parent reply other threads:[~2026-10-22 2:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 13:59 [PATCH v3 0/1] wifi: rtl8180: reject RX frames longer than MAX_RX_SIZE Jiaxin Li
2026-10-21 13:59 ` [PATCH v3 1/1] " Jiaxin Li
2026-10-22 2:49 ` Ping-Ke Shih [this message]
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=59bba0199d1a435f983d76a550929898@realtek.com \
--to=pkshih@realtek.com \
--cc=18135327133@163.com \
--cc=linux-wireless@vger.kernel.org \
/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