From: Blaise Boscaccy <bboscaccy@linux.microsoft.com>
To: bpf@vger.kernel.org, linux-security-module@vger.kernel.org,
kpsingh@kernel.org, bboscaccy@linux.microsoft.com,
paul@paul-moore.com, kys@microsoft.com, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org,
James.Bottomley@hansenpartnership.com, wufan@linux.microsoft.com,
qmo@kernel.org
Subject: [PATCH bpf-next v2 1/3] bpf: Add hash chain signature support for arbitrary maps
Date: Mon, 29 Sep 2025 14:34:25 -0700 [thread overview]
Message-ID: <20250929213520.1821223-2-bboscaccy@linux.microsoft.com> (raw)
In-Reply-To: <20250929213520.1821223-1-bboscaccy@linux.microsoft.com>
This patch introduces hash chain support for signature verification of
arbitrary bpf map objects which was described here:
https://lore.kernel.org/linux-security-module/20250721211958.1881379-1-kpsingh@kernel.org/
The UAPI is extended to allow for in-kernel checking of maps passed in
via the fd_array. A hash chain is constructed from the maps, in order
specified by the signature_maps field. The hash chain is terminated
with the hash of the program itself.
Tested-by: syzbot@syzkaller.appspotmail.com
Signed-off-by: Blaise Boscaccy <bboscaccy@linux.microsoft.com>
---
include/uapi/linux/bpf.h | 6 +++
kernel/bpf/syscall.c | 73 ++++++++++++++++++++++++++++++++--
tools/include/uapi/linux/bpf.h | 6 +++
3 files changed, 81 insertions(+), 4 deletions(-)
diff --git a/include/uapi/linux/bpf.h b/include/uapi/linux/bpf.h
index ae83d8649ef1c..a436a2ff49437 100644
--- a/include/uapi/linux/bpf.h
+++ b/include/uapi/linux/bpf.h
@@ -1621,6 +1621,12 @@ union bpf_attr {
* verification.
*/
__s32 keyring_id;
+ /* Pointer to a buffer containing the maps used in the signature
+ * hash chain of the BPF program.
+ */
+ __aligned_u64 signature_maps;
+ /* Size of the signature maps buffer. */
+ __u32 signature_maps_size;
};
struct { /* anonymous struct used by BPF_OBJ_* commands */
diff --git a/kernel/bpf/syscall.c b/kernel/bpf/syscall.c
index a48fa86f82a7f..f728f663765c4 100644
--- a/kernel/bpf/syscall.c
+++ b/kernel/bpf/syscall.c
@@ -2802,14 +2802,35 @@ static bool is_perfmon_prog_type(enum bpf_prog_type prog_type)
}
}
+static inline int bpf_map_get_hash(int map_fd, void *buffer)
+{
+ struct bpf_map *map;
+
+ CLASS(fd, f)(map_fd);
+ map = __bpf_map_get(f);
+ if (IS_ERR(map))
+ return PTR_ERR(map);
+
+ if (!map->ops->map_get_hash)
+ return -EINVAL;
+
+ return map->ops->map_get_hash(map, SHA256_DIGEST_SIZE, buffer);
+}
+
static int bpf_prog_verify_signature(struct bpf_prog *prog, union bpf_attr *attr,
bool is_kernel)
{
bpfptr_t usig = make_bpfptr(attr->signature, is_kernel);
- struct bpf_dynptr_kern sig_ptr, insns_ptr;
+ bpfptr_t umaps;
+ struct bpf_dynptr_kern sig_ptr, insns_ptr, hash_ptr;
struct bpf_key *key = NULL;
void *sig;
+ int *maps;
+ int map_fd;
int err = 0;
+ u64 buffer[SHA256_DIGEST_SIZE * 2 / sizeof(u64)];
+ u64 hash[SHA256_DIGEST_SIZE / sizeof(u64)];
+ int n;
if (system_keyring_id_check(attr->keyring_id) == 0)
key = bpf_lookup_system_key(attr->keyring_id);
@@ -2830,16 +2851,60 @@ static int bpf_prog_verify_signature(struct bpf_prog *prog, union bpf_attr *attr
bpf_dynptr_init(&insns_ptr, prog->insnsi, BPF_DYNPTR_TYPE_LOCAL, 0,
prog->len * sizeof(struct bpf_insn));
- err = bpf_verify_pkcs7_signature((struct bpf_dynptr *)&insns_ptr,
- (struct bpf_dynptr *)&sig_ptr, key);
+ if (!attr->signature_maps_size) {
+ err = bpf_verify_pkcs7_signature((struct bpf_dynptr *)&insns_ptr,
+ (struct bpf_dynptr *)&sig_ptr, key);
+ } else {
+ bpf_dynptr_init(&hash_ptr, hash, BPF_DYNPTR_TYPE_LOCAL, 0,
+ sizeof(hash));
+ umaps = make_bpfptr(attr->signature_maps, is_kernel);
+ maps = kvmemdup_bpfptr(umaps, attr->signature_maps_size * sizeof(*maps));
+ if (IS_ERR(maps)) {
+ err = PTR_ERR(maps);
+ goto out;
+ }
+ /* Process the map array in reverse order to generate a hash chain
+ * h(n) = sha256(h(n + 1), sha256(map(n)))
+ * h(n_len) = sha256(map(n_len))
+ */
+ for (n = attr->signature_maps_size - 1; n >= 0; n--) {
+ err = copy_from_bpfptr_offset(&map_fd,
+ make_bpfptr(attr->fd_array, is_kernel),
+ maps[n] * sizeof(map_fd),
+ sizeof(map_fd));
+ if (err)
+ goto free_maps;
+
+ if (n == attr->signature_maps_size - 1)
+ err = bpf_map_get_hash(map_fd, hash);
+ else {
+ memcpy(buffer, hash, sizeof(hash));
+ err = bpf_map_get_hash(map_fd, buffer + ARRAY_SIZE(hash));
+ sha256((u8 *)buffer, sizeof(buffer), (u8 *)&hash);
+ }
+ if (err)
+ goto free_maps;
+ }
+ /* Calculate final hash with program instructions
+ * f_hash = sha256(sha256(prog), h(0))
+ */
+ sha256((u8 *)prog->insnsi, prog->len * sizeof(struct bpf_insn), (u8 *)&buffer);
+ memcpy(buffer + ARRAY_SIZE(hash), hash, sizeof(hash));
+ sha256((u8 *)buffer, sizeof(buffer), (u8 *)&hash);
+ err = bpf_verify_pkcs7_signature((struct bpf_dynptr *)&hash_ptr,
+ (struct bpf_dynptr *)&sig_ptr, key);
+free_maps:
+ kvfree(maps);
+ }
+out:
bpf_key_put(key);
kvfree(sig);
return err;
}
/* last field in 'union bpf_attr' used by this command */
-#define BPF_PROG_LOAD_LAST_FIELD keyring_id
+#define BPF_PROG_LOAD_LAST_FIELD signature_maps_size
static int bpf_prog_load(union bpf_attr *attr, bpfptr_t uattr, u32 uattr_size)
{
diff --git a/tools/include/uapi/linux/bpf.h b/tools/include/uapi/linux/bpf.h
index ae83d8649ef1c..a436a2ff49437 100644
--- a/tools/include/uapi/linux/bpf.h
+++ b/tools/include/uapi/linux/bpf.h
@@ -1621,6 +1621,12 @@ union bpf_attr {
* verification.
*/
__s32 keyring_id;
+ /* Pointer to a buffer containing the maps used in the signature
+ * hash chain of the BPF program.
+ */
+ __aligned_u64 signature_maps;
+ /* Size of the signature maps buffer. */
+ __u32 signature_maps_size;
};
struct { /* anonymous struct used by BPF_OBJ_* commands */
--
2.48.1
next prev parent reply other threads:[~2025-09-29 21:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 21:34 [PATCH bpf-next v2 0/3] BPF signature hash chains Blaise Boscaccy
2025-09-29 21:34 ` Blaise Boscaccy [this message]
2025-09-29 21:34 ` [PATCH bpf-next v2 2/3] selftests/bpf: Enable map verification for some lskel tests Blaise Boscaccy
2025-09-29 21:34 ` [PATCH bpf-next v2 3/3] bpftool: Add support for signing program and map hash chains Blaise Boscaccy
2025-10-01 21:37 ` [PATCH bpf-next v2 0/3] BPF signature " Paul Moore
2025-10-02 13:48 ` KP Singh
2025-10-02 20:01 ` Blaise Boscaccy
2025-10-03 16:59 ` KP Singh
2025-10-03 18:14 ` Blaise Boscaccy
2025-10-03 19:02 ` KP Singh
2025-10-03 2:35 ` Paul Moore
2025-10-03 16:24 ` KP Singh
2025-10-06 3:08 ` Paul Moore
2025-10-07 13:53 ` KP Singh
2025-10-07 19:59 ` James Bottomley
2025-10-09 20:47 ` Paul Moore
2025-10-10 1:00 ` Alexei Starovoitov
2025-10-10 15:53 ` James Bottomley
2025-10-10 19:39 ` Paul Moore
2025-10-10 23:06 ` Alexei Starovoitov
2025-10-11 14:52 ` James Bottomley
2025-10-11 16:31 ` Alexei Starovoitov
2025-10-11 17:09 ` James Bottomley
2025-10-13 2:12 ` Paul Moore
2025-10-16 20:51 ` Paul Moore
2025-10-16 22:00 ` Alexei Starovoitov
2025-10-17 1:36 ` Paul Moore
2025-10-17 18:03 ` Alexei Starovoitov
2025-10-17 18:39 ` Paul Moore
2025-10-20 23:13 ` James Bottomley
2025-10-21 1:25 ` Alexei Starovoitov
2025-10-22 21:10 ` James Bottomley
2025-10-23 15:39 ` KP Singh
2025-10-23 17:53 ` Paul Moore
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=20250929213520.1821223-2-bboscaccy@linux.microsoft.com \
--to=bboscaccy@linux.microsoft.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kpsingh@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=qmo@kernel.org \
--cc=wufan@linux.microsoft.com \
/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