From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: "Pali Rohár" <pali@kernel.org>
Cc: Ben Greear <greearb@candelatech.com>,
Sasha Levin <sashal@kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
Stable <stable@vger.kernel.org>,
"open list:TI WILINK WIRELES..." <linux-wireless@vger.kernel.org>
Subject: Re: Drivers for Qualcomm wifi chips (ath*k) and security issues
Date: Mon, 23 Aug 2021 20:26:37 +0100 [thread overview]
Message-ID: <CADVatmPwp9Ngexm+_JgW3vBxFo6FBq9NzLS=POxHoO-COBQ0gA@mail.gmail.com> (raw)
In-Reply-To: <20210823145800.4vzdgzjch77ldeku@pali>
Hi Pali,
On Mon, Aug 23, 2021 at 3:58 PM Pali Rohár <pali@kernel.org> wrote:
>
> On Monday 23 August 2021 07:32:11 Ben Greear wrote:
> > On 8/23/21 7:08 AM, Pali Rohár wrote:
> > > Hello Sasha and Greg!
> > >
> > > Last week I sent request for backporting ath9k wifi fixes for security
> > > issue CVE-2020-3702 into stable LTS kernels because Qualcomm/maintainers
> > > did not it for more months... details are in email:
> > > https://lore.kernel.org/stable/20210818084859.vcs4vs3yd6zetmyt@pali/t/#u
> >
> > For one thing, almost everyone using these radios is using openwrt or
> > similar which has its own patch sets.
>
> AFAIK, latest stable released openwrt uses ath9k from 4.19 tree and
> AFAIK did not have above patch.
I think you asked for the following patches:
56c5485c9e44 ("ath: Use safer key clearing with key cache entries")
73488cb2fa3b ("ath9k: Clear key cache explicitly on disabling hardware")
d2d3e36498dd ("ath: Export ath_hw_keysetmac()")
144cd24dbc36 ("ath: Modify ath_key_delete() to not need full key entry")
ca2848022c12 ("ath9k: Postpone key cache entry deletion for TXQ frames
reference it")
And I can see they are already in the queue for next v4.19.y release,
so should be part of v4.19.205
--
Regards
Sudip
next prev parent reply other threads:[~2021-08-23 19:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 14:08 Drivers for Qualcomm wifi chips (ath*k) and security issues Pali Rohár
2021-08-23 14:32 ` Ben Greear
2021-08-23 14:54 ` Julian Calaby
2021-08-23 14:58 ` Pali Rohár
2021-08-23 19:26 ` Sudip Mukherjee [this message]
2021-08-23 20:02 ` Pali Rohár
2021-08-23 19:04 ` Greg KH
2021-10-11 10:41 ` Kalle Valo
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='CADVatmPwp9Ngexm+_JgW3vBxFo6FBq9NzLS=POxHoO-COBQ0gA@mail.gmail.com' \
--to=sudipm.mukherjee@gmail.com \
--cc=greearb@candelatech.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pali@kernel.org \
--cc=sashal@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).