From: Luka Gejak <luka.gejak@linux.dev>
To: Delene Tchio Romuald <delenetchior1@gmail.com>,
gregkh@linuxfoundation.org
Cc: error27@gmail.com, hansg@kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, luka.gejak@linux.dev
Subject: Re: [PATCH v6 0/5] staging: rtl8723bs: fix multiple security vulnerabilities
Date: Fri, 17 Apr 2026 09:26:24 +0200 [thread overview]
Message-ID: <71B54E47-F1DA-49A1-9742-3F70AA631607@linux.dev> (raw)
In-Reply-To: <20260417061048.62484-1-delenetchior1@gmail.com>
On April 17, 2026 8:10:43 AM GMT+02:00, Delene Tchio Romuald <delenetchior1@gmail.com> wrote:
>This series fixes five remotely-triggerable memory safety issues in
>the rtl8723bs driver. All of them are reachable from the air by an
>attacker within WiFi radio range, without authentication, via
>crafted management or data frames:
>
LGTM.
Reviewed-by: Luka Gejak <luka.gejak@linux.dev>
prev parent reply other threads:[~2026-04-17 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 6:10 [PATCH v6 0/5] staging: rtl8723bs: fix multiple security vulnerabilities Delene Tchio Romuald
2026-04-17 6:10 ` [PATCH v6 1/5] staging: rtl8723bs: fix heap buffer overflow in recvframe_defrag() Delene Tchio Romuald
2026-04-17 6:10 ` [PATCH v6 2/5] staging: rtl8723bs: fix integer underflow in TKIP MIC verification Delene Tchio Romuald
2026-04-17 6:10 ` [PATCH v6 3/5] staging: rtl8723bs: fix out-of-bounds read in portctrl() Delene Tchio Romuald
2026-04-17 6:10 ` [PATCH v6 4/5] staging: rtl8723bs: fix out-of-bounds reads in IE parsing functions Delene Tchio Romuald
2026-04-17 6:10 ` [PATCH v6 5/5] staging: rtl8723bs: fix negative length in WEP decryption Delene Tchio Romuald
2026-04-17 6:44 ` [PATCH v6 0/5] staging: rtl8723bs: fix multiple security vulnerabilities Dan Carpenter
2026-04-17 7:26 ` 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=71B54E47-F1DA-49A1-9742-3F70AA631607@linux.dev \
--to=luka.gejak@linux.dev \
--cc=delenetchior1@gmail.com \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox