All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: stable <stable@vger.kernel.org>, Sasha Levin <sashal@kernel.org>,
	Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
Subject: Re: Backport of 67c37756898a ("tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc") to older stable series? (at least 6.1.y)
Date: Wed, 10 Apr 2024 21:09:32 +0200	[thread overview]
Message-ID: <2024041054-asleep-replace-96e8@gregkh> (raw)
In-Reply-To: <ZhbiWp9DexB_gJh_@eldamar.lan>

On Wed, Apr 10, 2024 at 09:02:50PM +0200, Salvatore Bonaccorso wrote:
> Hi Greg, Sasha, Thadeu,
> 
> Today there was mentioning of 
> 
> https://www.jmpeax.dev/The-tale-of-a-GSM-Kernel-LPE.html
> 
> a LPE from the n_gsm module. I do realize, Thadeu mentioned the
> possible attack surface already back in
> 
> https://lore.kernel.org/all/ZMuRoDbMcQrsCs3m@quatroqueijos.cascardo.eti.br/#t
> 
> Published exploits are referenced as well through the potential
> initial finder in https://github.com/YuriiCrimson/ExploitGSM .
> 
> While 67c37756898a ("tty: n_gsm: require CAP_NET_ADMIN to attach
> N_GSM0710 ldisc") is not the fix itself, it helps mitigating against
> this issue.
> 
> Thus can you consider applying this still to the stable series as
> needed? I think it should go at least back to 5.15.y but if
> Iunderstood Thadeu correctly then even further back to the still
> supported stable branches.
> 
> What do you think?

Sure, I'll queue it up.  I think the "real" bugs there are already
resolved in the various older kernel trees, but adding this is "defense
in depth" and makes sense.

thanks,

greg k-h

      reply	other threads:[~2024-04-10 19:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 19:02 Backport of 67c37756898a ("tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc") to older stable series? (at least 6.1.y) Salvatore Bonaccorso
2024-04-10 19:09 ` Greg Kroah-Hartman [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=2024041054-asleep-replace-96e8@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=carnil@debian.org \
    --cc=cascardo@canonical.com \
    --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.