public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Heads up: Various Linux Kernel WiFi security issues (RCE/DOS) disclosed
Date: Sat, 15 Oct 2022 16:18:14 +0000	[thread overview]
Message-ID: <86c66ec4-9dd4-f505-41d4-9bd7a9d9fded@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1675 bytes --]

Hello development folks,

in case you have not noticed already, there are reports on a series of memory-related
security vulnerabilities in Linux' WiFi component, some with RCE potential, others "just"
allowing an adversary in WiFi proximity to DoS the system.

Please find more information here: https://www.openwall.com/lists/oss-security/2022/10/13/5

IPFire is vulnerable to all of these except for CVE-2022-42722, which requires a P2P
device to be set up on the victim system as a precondition for successful exploitation.

Patches are available (so is PoC exploit code), and have been merged into Linux 5.15.74,
released earlier today: https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.15.74

As for ready-to-use exploits, I have not seen anything arriving on exploit DB & friends,
but I guess that is a matter of time. Given the vulnerabilities' characteristics, however,
exploitation will likely be more of a wardiving style.

While there is no reason to panic, I would like to ship these fixes rather soon. Briefly
discussed this with Michael on the phone yesterday, and we both agree not to update the
kernel that is currently in Core Update 171 (which is anticipated to be released next
week).

However, I was thinking about cherry-picking the relevant (14) commits from kernel
5.15.74, which would greatly buy us time for Core Update 172, have our users protected,
and is less likely to cause collateral damage than shipping vanilla 5.15.74.

Should there be no vetoes on this until Tuesday morning, I would go for this option. As
always, any comments/critics/questions are greatly appreciated.

All the best,
Peter Müller

             reply	other threads:[~2022-10-15 16:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-15 16:18 Peter Müller [this message]
2022-10-17 13:35 ` Michael Tremer

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=86c66ec4-9dd4-f505-41d4-9bd7a9d9fded@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --cc=development@lists.ipfire.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