[PATCH] kernfs: recheck of->released after acquiring the active reference
Fan Wu <[email protected]>
| Newsgroups | dev.linux.lists.driver-core,org.kernel.vger.linux-kernel,org.kernel.vger.stable |
|---|---|
| Message-ID | <[email protected]> |
kernfs_get_active_of(), added by commit 3c9ba2777d6c ("kernfs: Fix UAF
in polling when open file is released"), tests @of->released before
acquiring the active reference on @of->kn. A hide/drain/show cycle can
run between those steps: the drain path releases the open file, and the
reactivation lets kernfs_get_active() succeed again. Any entry guarded
by kernfs_get_active_of() can consequently run its file operation on an
already released open file; on the cgroup pressure files, the poll
callback dereferences of->priv while forming &ctx->psi.trigger and can
hit either stale, freed memory or NULL.
CPU 0 (kernfs_fop_poll) CPU 1 (echo 0/1 > cgroup.pressure)
------------------------- ---------------------------------
of->released == false kernfs_show(kn, false)
... preempted ... kernfs_drain()
kernfs_release_file()
->release(of) (frees of->priv)
of->released = true
kernfs_show(kn, true)
kernfs_activate_one(kn)
kernfs_get_active(of->kn)
ops->poll(of)
The cycle needs the file operation to be delayed between the two
steps, but kernfs_show() cycles like the one above are fully
userspace driven.
Acquire the active reference first and re-check @of->released under
kernfs_open_file_mutex. While the reference is held, @kn cannot be
drained: kernfs_drain() waits for kn->active to reach
KN_DEACTIVATED_BIAS before draining open files, and the only other
kernfs_release_file() caller, kernfs_fop_release(), is serialized
against in-flight file operations by the VFS. Since
kernfs_release_file() sets @of->released under the same mutex, a
false re-read settles the question for good.
This issue was found by an in-house static analysis tool.
Fixes: 3c9ba2777d6c ("kernfs: Fix UAF in polling when open file is released")
Cc: [email protected]
Assisted-by: Codex:gpt-5.6
Signed-off-by: Fan Wu <[email protected]>
---
fs/kernfs/file.c | 16 +++++++++++++---
1 file changed, 13 insertions(+), 3 deletions(-)
diff --git a/fs/kernfs/file.c b/fs/kernfs/file.c
index 9adf36e6364b..561f66e4095a 100644
--- a/fs/kernfs/file.c
+++ b/fs/kernfs/file.c
@@ -73,12 +73,22 @@ static struct kernfs_open_node *of_on(struct kernfs_open_file *of)
/* Get active reference to kernfs node for an open file */
static struct kernfs_open_file *kernfs_get_active_of(struct kernfs_open_file *of)
{
- /* Skip if file was already released */
- if (unlikely(of->released))
+ if (!kernfs_get_active(of->kn))
return NULL;
- if (!kernfs_get_active(of->kn))
+ /*
+ * @of->released is set under kernfs_open_file_mutex. While the
+ * active reference is held, @kn can't be drained anymore and
+ * kernfs_fop_release() can't run, so re-reading @of->released
+ * here settles whether @of was released for good.
+ */
+ mutex_lock(kernfs_open_file_mutex_ptr(of->kn));
+ if (unlikely(of->released)) {
+ mutex_unlock(kernfs_open_file_mutex_ptr(of->kn));
+ kernfs_put_active(of->kn);
return NULL;
+ }
+ mutex_unlock(kernfs_open_file_mutex_ptr(of->kn));
return of;
}