From: Blaise Boscaccy <bboscaccy@linux.microsoft.com>
To: Tyler Hicks <code@tyhicks.com>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
"David Howells" <dhowells@redhat.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
"Paul Moore" <paul@paul-moore.com>,
"James Morris" <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nicolas Schier" <nicolas@fjasle.eu>,
"Shuah Khan" <shuah@kernel.org>,
"Mickaël Salaün" <mic@digikod.net>,
"Günther Noack" <gnoack@google.com>,
"Nick Desaulniers" <nick.desaulniers+lkml@gmail.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
"Jarkko Sakkinen" <jarkko@kernel.org>,
"Jan Stancek" <jstancek@redhat.com>,
"Neal Gompa" <neal@gompa.dev>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kbuild@vger.kernel.org, linux-kselftest@vger.kernel.org,
bpf@vger.kernel.org, llvm@lists.linux.dev, nkapron@google.com,
teknoraver@meta.com, roberto.sassu@huawei.com,
xiyou.wangcong@gmail.com
Subject: Re: [PATCH v2 security-next 1/4] security: Hornet LSM
Date: Mon, 14 Apr 2025 13:11:09 -0700 [thread overview]
Message-ID: <87lds2jyg2.fsf@microsoft.com> (raw)
In-Reply-To: <Z/lo3iVcJgB2pfQX@redbud>
Tyler Hicks <code@tyhicks.com> writes:
> On 2025-04-04 14:54:50, Blaise Boscaccy wrote:
>> +static int hornet_verify_lskel(struct bpf_prog *prog, struct hornet_maps *maps,
>> + void *sig, size_t sig_len)
>> +{
>> + int fd;
>> + u32 i;
>> + void *buf;
>> + void *new;
>> + size_t buf_sz;
>> + struct bpf_map *map;
>> + int err = 0;
>> + int key = 0;
>> + union bpf_attr attr = {0};
>> +
>> + buf = kmalloc_array(prog->len, sizeof(struct bpf_insn), GFP_KERNEL);
>> + if (!buf)
>> + return -ENOMEM;
>> + buf_sz = prog->len * sizeof(struct bpf_insn);
>> + memcpy(buf, prog->insnsi, buf_sz);
>> +
>> + for (i = 0; i < maps->used_map_cnt; i++) {
>> + err = copy_from_bpfptr_offset(&fd, maps->fd_array,
>> + maps->used_idx[i] * sizeof(fd),
>> + sizeof(fd));
>> + if (err < 0)
>> + continue;
>> + if (fd < 1)
>> + continue;
>> +
>> + map = bpf_map_get(fd);
>
> I'm not very familiar with BPF map lifetimes but I'd assume we need to have a
> corresponding bpf_map_put(map) before returning.
>
>> + if (IS_ERR(map))
>> + continue;
>> +
>> + /* don't allow userspace to change map data used for signature verification */
>> + if (!map->frozen) {
>> + attr.map_fd = fd;
>> + err = kern_sys_bpf(BPF_MAP_FREEZE, &attr, sizeof(attr));
>> + if (err < 0)
>> + goto out;
>> + }
>> +
>> + new = krealloc(buf, buf_sz + map->value_size, GFP_KERNEL);
>> + if (!new) {
>> + err = -ENOMEM;
>> + goto out;
>> + }
>> + buf = new;
>> + new = map->ops->map_lookup_elem(map, &key);
>> + if (!new) {
>> + err = -ENOENT;
>> + goto out;
>> + }
>> + memcpy(buf + buf_sz, new, map->value_size);
>> + buf_sz += map->value_size;
>> + }
>> +
>> + err = verify_pkcs7_signature(buf, buf_sz, sig, sig_len,
>> + VERIFY_USE_SECONDARY_KEYRING,
>> + VERIFYING_EBPF_SIGNATURE,
>> + NULL, NULL);
>> +out:
>> + kfree(buf);
>> + return err;
>> +}
>> +
>> +static int hornet_check_binary(struct bpf_prog *prog, union bpf_attr *attr,
>> + struct hornet_maps *maps)
>> +{
>> + struct file *file = get_task_exe_file(current);
>
> We should handle get_task_exe_file() returning NULL. I don't think it is likely
> to happen when passing `current` but kernel_read_file() doesn't protect against
> it and we'll have a NULL pointer dereference when it calls file_inode(NULL).
>
>> + const unsigned long markerlen = sizeof(EBPF_SIG_STRING) - 1;
>> + void *buf = NULL;
>> + size_t sz = 0, sig_len, prog_len, buf_sz;
>> + int err = 0;
>> + struct module_signature sig;
>> +
>> + buf_sz = kernel_read_file(file, 0, &buf, INT_MAX, &sz, READING_EBPF);
>
> We are leaking buf in this function. kernel_read_file() allocates the memory
> for us but we never kfree(buf).
>
>> + fput(file);
>> + if (!buf_sz)
>> + return -1;
>> +
>> + prog_len = buf_sz;
>> +
>> + if (prog_len > markerlen &&
>> + memcmp(buf + prog_len - markerlen, EBPF_SIG_STRING, markerlen) == 0)
>> + prog_len -= markerlen;
>
> Why is the marker optional? Looking at module_sig_check(), which verifies the
> signature on kernel modules, I see that it refuses to proceed if the marker is
> not found. Should we do the same and refuse to operate on any unexpected input?
>
Looking at this again, there doesn't seem to be a good reason to have an
optional marker. I'll get that fixed in v3 along with the rest of these
suggestions.
>> +
>> + memcpy(&sig, buf + (prog_len - sizeof(sig)), sizeof(sig));
>
> We should make sure that prog_len is larger than sizeof(sig) prior to this
> memcpy(). It is probably not a real issue in practice but it would be good to
> ensure that we can't be tricked to copy and operate on any bytes proceeding
> buf.
>
> Tyler
>
>> + sig_len = be32_to_cpu(sig.sig_len);
>> + prog_len -= sig_len + sizeof(sig);
>> +
>> + err = mod_check_sig(&sig, prog->len * sizeof(struct bpf_insn), "ebpf");
>> + if (err)
>> + return err;
>> + return hornet_verify_lskel(prog, maps, buf + prog_len, sig_len);
>> +}
next prev parent reply other threads:[~2025-04-14 20:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 21:54 [PATCH v2 security-next 0/4] Introducing Hornet LSM Blaise Boscaccy
2025-04-04 21:54 ` [PATCH v2 security-next 1/4] security: " Blaise Boscaccy
2025-04-06 4:27 ` kernel test robot
2025-04-06 20:42 ` kernel test robot
2025-04-11 19:09 ` Tyler Hicks
2025-04-14 20:11 ` Blaise Boscaccy [this message]
2025-04-11 23:16 ` [PATCH v2 " Paul Moore
2025-04-14 20:46 ` Blaise Boscaccy
2025-04-15 1:37 ` Paul Moore
2025-04-12 0:09 ` [PATCH v2 security-next " Alexei Starovoitov
2025-04-12 0:29 ` Matteo Croce
2025-04-12 0:57 ` Alexei Starovoitov
2025-04-12 14:11 ` Blaise Boscaccy
2025-04-12 13:57 ` Blaise Boscaccy
2025-04-14 16:08 ` Paul Moore
2025-04-14 20:56 ` Alexei Starovoitov
2025-04-15 0:32 ` Blaise Boscaccy
2025-04-15 1:38 ` Alexei Starovoitov
2025-04-15 15:45 ` Blaise Boscaccy
2025-04-15 19:08 ` Blaise Boscaccy
2025-04-19 16:21 ` Paul Moore
2025-04-15 21:48 ` Alexei Starovoitov
2025-04-16 17:31 ` Blaise Boscaccy
2025-04-21 20:12 ` Alexei Starovoitov
2025-04-21 22:03 ` Paul Moore
2025-04-21 23:48 ` Alexei Starovoitov
2025-04-22 2:38 ` Paul Moore
2025-04-23 14:12 ` James Bottomley
2025-04-23 15:10 ` Paul Moore
2025-04-24 23:41 ` Alexei Starovoitov
2025-04-25 14:06 ` James Bottomley
2025-04-25 21:44 ` Blaise Boscaccy
2025-04-19 18:43 ` James Bottomley
2025-04-21 18:52 ` Paul Moore
2025-04-21 19:03 ` James Bottomley
2025-04-04 21:54 ` [PATCH v2 security-next 2/4] hornet: Introduce sign-ebpf Blaise Boscaccy
2025-04-04 21:54 ` [PATCH v2 security-next 3/4] hornet: Add a light skeleton data extractor script Blaise Boscaccy
2025-04-04 21:54 ` [PATCH v2 security-next 4/4] selftests/hornet: Add a selftest for the Hornet LSM Blaise Boscaccy
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=87lds2jyg2.fsf@microsoft.com \
--to=bboscaccy@linux.microsoft.com \
--cc=bpf@vger.kernel.org \
--cc=code@tyhicks.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=gnoack@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=jarkko@kernel.org \
--cc=jmorris@namei.org \
--cc=jstancek@redhat.com \
--cc=justinstitt@google.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=mic@digikod.net \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=neal@gompa.dev \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=nicolas@fjasle.eu \
--cc=nkapron@google.com \
--cc=paul@paul-moore.com \
--cc=roberto.sassu@huawei.com \
--cc=serge@hallyn.com \
--cc=shuah@kernel.org \
--cc=teknoraver@meta.com \
--cc=xiyou.wangcong@gmail.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;
as well as URLs for NNTP newsgroup(s).