From: "Luka Gejak" <luka.gejak@linux.dev>
To: "Feng Ning" <feng@innora.ai>, <gregkh@linuxfoundation.org>
Cc: <linux-staging@lists.linux.dev>
Subject: Re: [PATCH v3] staging: rtl8723bs: fix heap buffer overflow in cfg80211_rtw_add_key
Date: Wed, 08 Apr 2026 18:19:21 +0200 [thread overview]
Message-ID: <DHNWRM5936LY.2U3AXP4KDHHCX@linux.dev> (raw)
In-Reply-To: <20260408150019.16368-1-feng@innora.ai>
On Wed Apr 8, 2026 at 5:00 PM CEST, Feng Ning wrote:
> The cfg80211 framework allows key sequence counters (NL80211_KEY_SEQ)
> up to 16 bytes, but ieee_param.crypt.seq is a fixed 8-byte buffer.
> When cfg80211_rtw_add_key() copies the sequence counter via memcpy()
> without checking seq_len, a heap buffer overflow of up to 8 bytes
> occurs, overwriting adjacent fields key_len and key[].
>
> Cap the copy length at the buffer size using min_t().
>
> Fixes: 554c0a3abf21 ("staging: Add rtl8723bs sdio wifi driver")
> Signed-off-by: Feng Ning <feng@innora.ai>
> ---
> Changes v2 -> v3:
> - Added changelog below the cut line (per patch-bot feedback)
> - No code changes from v2
>
> Changes v1 -> v2:
> - Initial public submission to linux-staging mailing list
>
...
Hi Feng,
thanks for v3, however this patch can not be accepted as is.
First, of all you should configure and use git send-email for submiting
patches as your emails should be pure plaintext.
Secondly, your emails contain attachments which are not accepted for
patches.
Thirdly, you should not include your gpg key because as I previously
said no attachments.
Please read Documentation/process/submitting-patches.rst file for more
info. Logic itself is sound.
Best regards,
Luka Gejak
prev parent reply other threads:[~2026-04-08 16:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 15:00 [PATCH v3] staging: rtl8723bs: fix heap buffer overflow in cfg80211_rtw_add_key Feng Ning
2026-04-08 16:19 ` Luka Gejak [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=DHNWRM5936LY.2U3AXP4KDHHCX@linux.dev \
--to=luka.gejak@linux.dev \
--cc=feng@innora.ai \
--cc=gregkh@linuxfoundation.org \
--cc=linux-staging@lists.linux.dev \
/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