From: Greg KH <gregkh@linuxfoundation.org>
To: Pavel Machek <pavel@denx.de>
Cc: nobuhiro1.iwamatsu@toshiba.co.jp, "Pali Rohár" <pali@kernel.org>,
stable@vger.kernel.org, "Sasha Levin" <sashal@kernel.org>,
"Kalle Valo" <kvalo@codeaurora.org>,
linux-wireless@vger.kernel.org
Subject: Re: Backporting CVE-2020-3702 ath9k patches to stable
Date: Thu, 2 Sep 2021 14:02:08 +0200 [thread overview]
Message-ID: <YTC9QBWPoulIhZYq@kroah.com> (raw)
In-Reply-To: <20210902114814.GA525@amd>
On Thu, Sep 02, 2021 at 01:48:14PM +0200, Pavel Machek wrote:
> Hi!
>
> > > > > Hello! I would like to request for backporting following ath9k commits
> > > > > which are fixing CVE-2020-3702 issue.
> > > > >
> > > > > 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")
> > > > >
> > > > > See also:
> > > > > https://lore.kernel.org/linux-wireless/87o8hvlx5g.fsf@codeaurora.org/
> ...
> > > > What stable tree(s) do you want to see these go into?
> > >
> > > Commits were introduced in 5.12, so it should go to all stable trees << 5.12
>
> ...
>
> > Great, all now queued up. Sad that qcom didn't want to do this
> > themselves :(
>
> Thanks for the fixes; I see them in 4.14 and newer stable trees.
>
> But I don't see them in 4.4 and 4.9, nor can I see reason why they
> were not applied.
>
> Can someone help?
Odd, I don't remember why I didn't even try to apply them to older
kernels. I'll do that after this next round is released in a few days,
sorry about that.
greg k-h
next prev parent reply other threads:[~2021-09-02 12:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 8:48 Backporting CVE-2020-3702 ath9k patches to stable Pali Rohár
2021-08-18 9:02 ` Greg KH
2021-08-18 9:10 ` Pali Rohár
2021-08-18 9:18 ` Greg KH
2021-08-20 11:35 ` Pali Rohár
2021-08-20 21:23 ` Sasha Levin
2021-08-20 22:27 ` Toke Høiland-Jørgensen
2021-08-20 23:07 ` Pali Rohár
2021-08-20 23:49 ` Sasha Levin
2021-08-20 22:41 ` Pali Rohár
2021-09-02 11:48 ` Pavel Machek
2021-09-02 12:02 ` Greg KH [this message]
2021-09-03 6:34 ` Pavel Machek
2021-09-06 8:49 ` Greg KH
2021-09-11 7:46 ` Pavel Machek
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=YTC9QBWPoulIhZYq@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=pali@kernel.org \
--cc=pavel@denx.de \
--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 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.