Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: IM <grayhat@foxmail.com>
Cc: security <security@kernel.org>, stable <stable@vger.kernel.org>
Subject: Re: [SECURITY] userfaultfd ioctl bypass and ksmbd FSCTL permission bypass
Date: Mon, 25 May 2026 21:17:32 +0200	[thread overview]
Message-ID: <2026052526-cacti-twiddle-53f3@gregkh> (raw)
In-Reply-To: <tencent_DEF21A96480ED4822654DC73A74623394C09@qq.com>

On Mon, May 25, 2026 at 05:23:04PM +0800, IM wrote:
> Hi,
> 
> 
> We identified two vulnerabilities in the Linux kernel during a recent
> security audit. Neither has been fixed in any released version. Details
> and patches are below.

Nice, but why send this to a public list?  Please just resend your
patches properly, to the correct maintainers and lists for the different
subsystems, so they can be applied.

thanks,

greg k-h

  reply	other threads:[~2026-05-25 19:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-25  9:23 [SECURITY] userfaultfd ioctl bypass and ksmbd FSCTL permission bypass IM
2026-05-25 19:17 ` Greg KH [this message]
     [not found] ` <tencent_AE575EFF92D5814710A0CA476EDFA82E0706@qq.com>
2026-05-26  6:36   ` 回复:[SECURITY] " Greg KH

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=2026052526-cacti-twiddle-53f3@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=grayhat@foxmail.com \
    --cc=security@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