All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "�������� / �л� / ���⡤�������к�" <sihyeonroh@snu.ac.kr>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"security@kernel.org" <security@kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [Linux bug report] A bug breaking device drivers' fault isolation guarantees
Date: Mon, 10 Jun 2024 17:05:26 +0200	[thread overview]
Message-ID: <2024061055-shone-clean-3d0d@gregkh> (raw)
In-Reply-To: <PS2P216MB12517ED0C28EFD7FA0B3FAEAF9C62@PS2P216MB1251.KORP216.PROD.OUTLOOK.COM>

On Mon, Jun 10, 2024 at 02:58:16PM +0000, �������� / �л� / ���⡤�������к� wrote:
> Hi,
> I'm Sihyun Roh, a security researcher at Compsec Lab, Seoul National University.
> While testing NVIDIA GPU code, I discovered a minor mistake in the Linux kernel code. This issue can cause one process's fault to affect other processes, compromising the fault isolation guarantee. Given the potential security implications, I am forwarding this to the security team as well.
> If you have any questions, feel free to ask.
> Thank you for your efforts in maintaining the Linux kernel code.
> Sincerely,
> Sihyun


For obvious reasons we can't open unsolicited .pdf files.  Can you send
this in text format?

And if this is for an out-of-tree kernel driver, there's nothing we can
do about that :(

thanks,

greg k-h


       reply	other threads:[~2024-06-10 15:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <PS2P216MB12517ED0C28EFD7FA0B3FAEAF9C62@PS2P216MB1251.KORP216.PROD.OUTLOOK.COM>
2024-06-10 15:05 ` Greg KH [this message]
     [not found]   ` <PS2P216MB1251E30AB1226BC4FF1150FFF9C62@PS2P216MB1251.KORP216.PROD.OUTLOOK.COM>
2024-06-11  2:35     ` [Linux bug report] A bug breaking device drivers' fault isolation guarantees Alistair Popple
2024-06-11  4:41       ` ­노시현 / 학생 / 전기·정보공학부

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=2024061055-shone-clean-3d0d@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=security@kernel.org \
    --cc=sihyeonroh@snu.ac.kr \
    /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.