mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hungyu Lin <dennylin0707@gmail.com>
To: tony.luck@intel.com, reinette.chatre@intel.com
Cc: x86@kernel.org, Dave.Martin@arm.com, james.morse@arm.com,
	babu.moger@amd.com, tglx@kernel.org, fenghua.yu@intel.com,
	josef@toxicpanda.com, linux-kernel@vger.kernel.org,
	sashiko-bot@kernel.org, dennylin0707@gmail.com
Subject: [PATCH] fs/resctrl: Use open-time credentials for task move permission checks
Date: Sat,  7 Nov 2026 09:32:53 +0000	[thread overview]
Message-ID: <20261107093253.62518-1-dennylin0707@gmail.com> (raw)

Writing a PID to a resctrl group's "tasks" file moves that task into the
group. Whether the move is allowed depends on the PID written, so
rdtgroup_task_write_permission() checks it at write time, making the
same comparisons as __cgroup1_procs_write().

It checks current's credentials. That may allow a less privileged
process to trick a more privileged one into writing into a fd that it
opened. Commit 1756d7994ad8 ("cgroup: Use open-time credentials for
process migraton perm checks") closed the same hole in cgroup by using
the credentials saved at open time. rdtgroup_task_write_permission()
still uses current_cred().

Use of->file->f_cred instead, as cgroup1 does.

Fixes: e02737d5b826 ("x86/intel_rdt: Add tasks files")
Signed-off-by: Hungyu Lin <dennylin0707@gmail.com>
---
Compile tested only, x86_64 and arm64 with W=1. I don't have hardware
with RDT, PQoS or MPAM to run it on.

By default only root can open the "tasks" file for writing, so this
only matters when write access to a resource group has been handed to
a less privileged user.

This changes the comment that Josef Bacik's "fs/resctrl: use
cred_ids_allow_move()" uses as context. A plain git apply of that patch
on top of this one fails; git am -3 merges the two cleanly.

 fs/resctrl/rdtgroup.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/fs/resctrl/rdtgroup.c b/fs/resctrl/rdtgroup.c
index 57ab090072c2..ddaf34548205 100644
--- a/fs/resctrl/rdtgroup.c
+++ b/fs/resctrl/rdtgroup.c
@@ -725,12 +725,14 @@ static int rdtgroup_task_write_permission(struct task_struct *task,
 					  struct kernfs_open_file *of)
 {
 	const struct cred *tcred = get_task_cred(task);
-	const struct cred *cred = current_cred();
+	const struct cred *cred = of->file->f_cred;
 	int ret = 0;

 	/*
 	 * Even if we're attaching all tasks in the thread group, we only
-	 * need to check permissions on one of them.
+	 * need to check permissions on one of them. Check permissions using
+	 * the credentials from file open to protect against inherited fd
+	 * attacks.
 	 */
 	if (!uid_eq(cred->euid, GLOBAL_ROOT_UID) &&
 	    !uid_eq(cred->euid, tcred->uid) &&
--
2.43.0

                 reply	other threads:[~2026-11-07  9:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261107093253.62518-1-dennylin0707@gmail.com \
    --to=dennylin0707@gmail.com \
    --cc=Dave.Martin@arm.com \
    --cc=babu.moger@amd.com \
    --cc=fenghua.yu@intel.com \
    --cc=james.morse@arm.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reinette.chatre@intel.com \
    --cc=sashiko-bot@kernel.org \
    --cc=tglx@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=x86@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

all inboxes | Powered by JetHome®