From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Laxman Acharya Padhya <acharyalaxman8848@gmail.com>
Cc: Hans de Goede <hansg@kernel.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: validate WPS attribute lengths
Date: Sun, 2 Aug 2026 10:16:26 +0200 [thread overview]
Message-ID: <2026080254-deflector-mystify-a2ec@gregkh> (raw)
In-Reply-To: <CAMyXUJm_m79_0D8a_PWLnouN7NaF4aBsd3r9doKWyrKncN0aHA@mail.gmail.com>
On Sun, Aug 02, 2026 at 01:57:09PM +0545, Laxman Acharya Padhya wrote:
> Hi Greg,
>
> This was found during an OpenAI Codex-assisted static
> review. Codex helped identify the unchecked length and draft the initial
> change; I then traced the call sites. I should have disclosed that
> assistance in the original submission.
Please do so.
> The reachable path is through received scan results:
> rtw_cfg80211_inform_bss() parses a WPS IE and copies the Selected Registrar
> payload into the one-byte stack variable `sr`. The outer IE is validated,
> but the inner attribute length was not. An oversized payload can therefore
> overwrite `sr`. An attribute length of 0xffff also makes the old u16
> attr_len calculation wrap to 3, after which attr_len - 4 underflows before
> memcpy().
>
> I ran git diff --check, strict checkpatch (no errors or warnings), and a
> Docker ARM64 W=1 build with CONFIG_RTL8723BS=m. I did not test on hardware
> or inject a malformed frame, so testing was compile and static analysis
> only. I will include the appropriate Assisted-by information and improve
> runtime testing before any revision.
Please test stuff like this on real hardware, so we know you didn't
break anything.
thanks,
greg k-h
prev parent reply other threads:[~2026-08-02 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 17:46 [PATCH] staging: rtl8723bs: validate WPS attribute lengths Laxman Acharya Padhya
2026-08-02 7:16 ` Greg Kroah-Hartman
2026-08-02 8:12 ` Laxman Acharya Padhya
2026-08-02 8:16 ` Greg Kroah-Hartman [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=2026080254-deflector-mystify-a2ec@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=acharyalaxman8848@gmail.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.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