From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Kuzey Arda Bulut <kuzeyb.business@gmail.com>
Cc: security@kernel.org, jirislaby@kernel.org,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: Subject: [SECURITY] Vulnerability in Linux Kernel
Date: Thu, 30 May 2024 07:19:02 +0200 [thread overview]
Message-ID: <2024053036-villain-backlight-d92b@gregkh> (raw)
In-Reply-To: <CAKmisHAUUqQ-7F+7BOymY7_3XBT1FE=gskraKDC1OmySZgS0yA@mail.gmail.com>
On Wed, May 29, 2024 at 08:25:18PM +0300, Kuzey Arda Bulut wrote:
> Dear Linux Kernel Security Team,
>
> I have discovered a null-ptr-deref security vulnerability in tty driver in
> the Linux kernel. You can find the detailed descriptions of the
> vulnerability in report.md.
>
> If you have any questions or need further information, please do not
> hesitate to contact me.
As the n_gsm is full of known issues by the developers, and the ldisc is
not allowed to be loaded by a non-root user, this isn't all that serious
of an issue. See this thread for a list of problems that I think you
might have already found here:
https://lore.kernel.org/r/DB9PR10MB5881D2170678C169FB42A423E0082@DB9PR10MB5881.EURPRD10.PROD.OUTLOOK.COM
Note, 2 fixes have landed in 6.10-rc2 for this driver, can you verify if
these fix the issue you are reporting here?
And do you have a proposed fix for this issue?
thanks,
greg k-h
next parent reply other threads:[~2024-05-30 5:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKmisHAUUqQ-7F+7BOymY7_3XBT1FE=gskraKDC1OmySZgS0yA@mail.gmail.com>
2024-05-30 5:19 ` gregkh [this message]
2024-05-30 5:19 ` Subject: [SECURITY] Vulnerability in Linux Kernel gregkh
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=2024053036-villain-backlight-d92b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=kuzeyb.business@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=security@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.