From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Linux List Kernel Mailing <linux-wireless@vger.kernel.org>,
sean.wang@mediatek.com, deren.wu@mediatek.com,
Felix Fietkau <nbd@nbd.name>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: BUG: KASAN: vmalloc-out-of-bounds in mt7921_check_offload_capability+0x3fa/0x430 [mt7921_common]
Date: Tue, 21 Mar 2023 05:04:59 +0500 [thread overview]
Message-ID: <CABXGCsMP6XUt4QKPc2P4fHo8DD_tam62NBHGrSWc0BHvch3hXw@mail.gmail.com> (raw)
In-Reply-To: <121d75eb-da8e-e120-3754-391a0c064001@candelatech.com>
On Mon, Mar 20, 2023 at 7:00 PM Ben Greear <greearb@candelatech.com> wrote:
>
> On 3/20/23 03:32, Mikhail Gavrilov wrote:
> > Hi,
> > After enabling KASAN sanitizer the message "BUG: KASAN:
> > vmalloc-out-of-bounds in mt7921_check_offload_capability+0x3fa/0x430
> > [mt7921_common]" chase me at every boot.
>
> This is use-after-free bug, and I already posted a patch to fix it.
> "wireless: mt76: mt7921: Fix use-after-free in fw features query."
Hi,
This is the last version?
https://patchwork.kernel.org/project/linux-wireless/patch/20230308175832.2394061-1-greearb@candelatech.com/
Unfortunately it is not applicable to 6.3-rc3.
❯ git apply v2-wireless-mt76-mt7921-Fix-use-after-free-in-fw-features-query..patch
-v
Checking patch drivers/net/wireless/mediatek/mt76/mt7921/init.c...
Hunk #1 succeeded at 171 (offset 6 lines).
Hunk #2 succeeded at 203 (offset 6 lines).
error: while searching for:
release_firmware(fw);
return features ? features->data : 0;
}
EXPORT_SYMBOL_GPL(mt7921_check_offload_capability);
error: patch failed: drivers/net/wireless/mediatek/mt76/mt7921/init.c:211
error: drivers/net/wireless/mediatek/mt76/mt7921/init.c: patch does not apply
--
Best Regards,
Mike Gavrilov.
prev parent reply other threads:[~2023-03-21 0:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 10:32 Mikhail Gavrilov
2023-03-20 14:00 ` Ben Greear
2023-03-21 0:04 ` Mikhail Gavrilov [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=CABXGCsMP6XUt4QKPc2P4fHo8DD_tam62NBHGrSWc0BHvch3hXw@mail.gmail.com \
--to=mikhail.v.gavrilov@gmail.com \
--cc=deren.wu@mediatek.com \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=sean.wang@mediatek.com \
/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
all inboxes | Powered by JetHome®