From: Greg KH <gregkh@linuxfoundation.org>
To: Muhammad Bilal <meatuni001@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2 0/3] staging: rtl8723bs: fix multiple OOB reads in IE and frame parsing
Date: Tue, 25 Aug 2026 09:29:34 +0200 [thread overview]
Message-ID: <2026082555-balancing-facility-6e54@gregkh> (raw)
In-Reply-To: <CADqcGBko4B8hEXkgG6LCb9HXoW5HdcTNBAuWh6CQN2cURgkT-A@mail.gmail.com>
Please do not top-post.
On Tue, Aug 25, 2026 at 12:22:54PM +0500, Muhammad Bilal wrote:
> Apologies for the context-less ping, that was on me.
>
> For reference, this is the v2 series (sent Jul 28) fixing three OOB read /
> stack overflow bugs in rtl8723bs where length or offset fields from
> untrusted wireless frames are used without validating that enough bytes
> remain in the buffer:
>
> 1/3 fix OOB read / stack overflow in rtw_get_wps_attr()
> 2/3 fix OOB read in rtw_action_frame_parse()
> 3/3 fix OOB read in rtw_restruct_wmm_ie()
>
> It's been about four weeks with no review comments. Just checking whether
> the series is still on your radar, or if there's anything you'd like
> changed before it can be applied.
It's in my queue to review, it's the middle of the merge window right
now and nothing can be done until after -rc1 happens.
Also, have you tested this on real hardware?
thanks,
greg k-h
next prev parent reply other threads:[~2026-08-25 7:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 12:54 [PATCH v2 0/3] staging: rtl8723bs: fix multiple OOB reads in IE and frame parsing Muhammad Bilal
2026-07-28 12:54 ` [PATCH v2 1/3] staging: rtl8723bs: fix OOB read / stack overflow in rtw_get_wps_attr() Muhammad Bilal
2026-07-28 12:54 ` [PATCH v2 2/3] staging: rtl8723bs: fix OOB read in rtw_action_frame_parse() Muhammad Bilal
2026-07-28 12:54 ` [PATCH v2 3/3] staging: rtl8723bs: fix OOB read in rtw_restruct_wmm_ie() Muhammad Bilal
2026-08-24 23:10 ` [PATCH v2 0/3] staging: rtl8723bs: fix multiple OOB reads in IE and frame parsing Muhammad Bilal
2026-08-25 5:26 ` Greg KH
[not found] ` <CADqcGBko4B8hEXkgG6LCb9HXoW5HdcTNBAuWh6CQN2cURgkT-A@mail.gmail.com>
2026-08-25 7:23 ` Muhammad Bilal
2026-08-25 7:29 ` Greg KH [this message]
2026-08-25 10:25 ` Muhammad Bilal
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=2026082555-balancing-facility-6e54@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=meatuni001@gmail.com \
--cc=stable@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 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.