From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,roman.gushchin@linux.dev,pimyn@google.com,gthelen@google.com,elver@google.com,glider@google.com,akpm@linux-foundation.org
Subject: [merged mm-nonmm-stable] kfence-fix-kasan-hw-tags-bypass-via-runtime-sample_interval-change.patch removed from -mm tree
Date: Thu, 28 May 2026 21:26:03 -0700 [thread overview]
Message-ID: <20260529042603.A32EF1F00899@smtp.kernel.org> (raw)
The quilt patch titled
Subject: kfence: fix KASAN HW tags bypass via runtime sample_interval change
has been removed from the -mm tree. Its filename was
kfence-fix-kasan-hw-tags-bypass-via-runtime-sample_interval-change.patch
This patch was dropped because it was merged into the mm-nonmm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Alexander Potapenko <glider@google.com>
Subject: kfence: fix KASAN HW tags bypass via runtime sample_interval change
Date: Thu, 7 May 2026 11:52:37 +0200
If a user writes a non-zero value to the sample_interval module parameter
at runtime, the missing KASAN HW tags check in the late init path allows
KFENCE to be enabled alongside KASAN HW tags, bypassing the boot
restriction.
This patch adds the missing check to param_set_sample_interval() to reject
the parameter change if KASAN HW tags are enabled.
Link: https://lore.kernel.org/20260507095237.741017-1-glider@google.com
Fixes: 09833d99db36 ("mm/kfence: disable KFENCE upon KASAN HW tags enablement")
Signed-off-by: Alexander Potapenko <glider@google.com>
Cc: Marco Elver <elver@google.com>
Cc: Greg Thelen <gthelen@google.com>
Cc: Roman Gushchin <roman.gushchin@linux.dev>
Cc: Pimyn Girgis <pimyn@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/kfence/core.c | 5 +++++
1 file changed, 5 insertions(+)
--- a/mm/kfence/core.c~kfence-fix-kasan-hw-tags-bypass-via-runtime-sample_interval-change
+++ a/mm/kfence/core.c
@@ -77,6 +77,11 @@ static int param_set_sample_interval(con
WRITE_ONCE(kfence_enabled, false);
}
+ if (num && kasan_hw_tags_enabled()) {
+ pr_info("disabled as KASAN HW tags are enabled\n");
+ return -EINVAL;
+ }
+
*((unsigned long *)kp->arg) = num;
if (num && !READ_ONCE(kfence_enabled) && system_state != SYSTEM_BOOTING)
_
Patches currently in -mm which might be from glider@google.com are
lib-test_meminit-use-for-bools.patch
reply other threads:[~2026-05-29 4:26 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=20260529042603.A32EF1F00899@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=gthelen@google.com \
--cc=mm-commits@vger.kernel.org \
--cc=pimyn@google.com \
--cc=roman.gushchin@linux.dev \
/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.