From: Ping-Ke Shih <pkshih@realtek.com>
To: Falconet3 <Falconet3@proton.me>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] wifi: rtw89: fix OOB read past firmware buffer when duplicating elements
Date: Sun, 22 Nov 2026 01:31:58 +0000 [thread overview]
Message-ID: <2fb081759df841aa9d22df3ce43430be@realtek.com> (raw)
In-Reply-To: <ONBhkh_B7hyKoHNRpjYgxy7da68QOa8cWUqztT-I1nW-KukOKE30FIYFLkX1Tm_TrXlBjse5d-AFRwsyzfxBdMGKvyIEoVsjyZQqxzUkRQk=@proton.me>
Falconet3 <Falconet3@proton.me> wrote:
> Fix for an OOB read (up to 31 bytes past the firmware buffer) introduced in v7.4-rc1 by the fw-element
> copy-on-parse rework. Patch attached, applies to v7.4-rc3. Thanks!
Please rephrase commit message generated by LLM and send patch inline.
---
pw-bot: cr
prev parent reply other threads:[~2026-11-22 1:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-22 0:06 [PATCH] wifi: rtw89: fix OOB read past firmware buffer when duplicating elements Falconet3
2026-11-22 1:31 ` 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=2fb081759df841aa9d22df3ce43430be@realtek.com \
--to=pkshih@realtek.com \
--cc=Falconet3@proton.me \
--cc=linux-kernel@vger.kernel.org \
--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