linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
	stable@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Drivers for Qualcomm wifi chips (ath*k) and security issues
Date: Mon, 23 Aug 2021 21:04:27 +0200	[thread overview]
Message-ID: <YSPxO+VGnSopgn5G@kroah.com> (raw)
In-Reply-To: <20210823140844.q3kx6ruedho7jen5@pali>

On Mon, Aug 23, 2021 at 04:08:44PM +0200, 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
> 
> And now I got reports that in stable LTS kernels (4.14, 4.19) are
> missing also other fixes for other Qualcomm wifi security issues,
> covered by FragAttacks codename: CVE-2020-26145 CVE-2020-26139
> CVE-2020-26141

Then someone needs to provide us backports if they care about these
very old kernels and these issues.  Just like any other driver subsystem
where patches are not able to be easily backported.

Or just use a newer kernel, that's almost always a better idea.

thanks,

greg k-h

  parent reply	other threads:[~2021-08-24  6:43 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
2021-08-23 20:02       ` Pali Rohár
2021-08-23 19:04 ` Greg KH [this message]
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=YSPxO+VGnSopgn5G@kroah.com \
    --to=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).