Linux Power Management development
 help / color / mirror / Atom feed
From: Yunseong Kim <ysk@kzalloc.com>
To: Christian Brauner <brauner@kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>
Cc: Jan Kara <jack@suse.cz>, "Rafael J. Wysocki" <rafael@kernel.org>,
	Pavel Machek <pavel@kernel.org>, Len Brown <len.brown@intel.com>,
	byungchul@sk.com, max.byungchul.park@gmail.com,
	linux-fsdevel@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: Prevent panic from NULL dereference in alloc_fs_context() during do_exit()
Date: Tue, 6 May 2025 18:42:21 +0900	[thread overview]
Message-ID: <4dcff9ce-4ec8-4b57-9f21-a7e2f37b4d5c@kzalloc.com> (raw)
In-Reply-To: <20250506-hochphase-kicken-7fa895216c2a@brauner>

Hi Christian,

On 5/6/25 5:45 오후, Christian Brauner wrote:
>>> diff --git a/fs/fs_context.c b/fs/fs_context.c
>>> index 582d33e81117..529de43b8b5e 100644
>>> --- a/fs/fs_context.c
>>> +++ b/fs/fs_context.c
>>> @@ -282,6 +282,9 @@ static struct fs_context *alloc_fs_context(struct file_system_type *fs_type,
>>>  	struct fs_context *fc;
>>>  	int ret = -ENOMEM;
>>>  
>>> +	if (!current->nsproxy || !current->nsproxy->net_ns)
>>> +		return ERR_PTR(-EINVAL);
>>> +
>>>  	fc = kzalloc(sizeof(struct fs_context), GFP_KERNEL_ACCOUNT);
>>>  	if (!fc)
>>>  		return ERR_PTR(-ENOMEM);
>>
>> That might paper over the oops, but I very much doubt that this will be
>> a correct fix...  Note that in efivarfs_pm_notify() we have other
>> fun issues when run from such context - have task_work_add() fail in
>> fput() and if delayed_fput() runs right afterwards and
>>         efivar_init(efivarfs_check_missing, sfi->sb, false);
>> in there might end up with UAF...
> 
> We've already accepted a patch that removes the need for
> vfs_kern_mount() from efivarfs completely.

I’ll take a look at the patch you mentioned, check if the issue reproduces, and get back to you.

Link: https://lore.kernel.org/all/20250318194111.19419-4-James.Bottomley@HansenPartnership.com/

Thanks for checking it!

Best regards,
Yunseong Kim


      reply	other threads:[~2025-05-06  9:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-05 20:38 [PATCH] fs: Prevent panic from NULL dereference in alloc_fs_context() during do_exit() Yunseong Kim
2025-05-05 22:36 ` Al Viro
2025-05-05 22:58   ` Yunseong Kim
2025-05-06  8:45   ` Christian Brauner
2025-05-06  9:42     ` Yunseong Kim [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=4dcff9ce-4ec8-4b57-9f21-a7e2f37b4d5c@kzalloc.com \
    --to=ysk@kzalloc.com \
    --cc=brauner@kernel.org \
    --cc=byungchul@sk.com \
    --cc=jack@suse.cz \
    --cc=len.brown@intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=max.byungchul.park@gmail.com \
    --cc=pavel@kernel.org \
    --cc=rafael@kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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