From: Paul Moore <paul@paul-moore.com>
To: Jann Horn <jannh@google.com>, James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>
Cc: Casey Schaufler <casey@schaufler-ca.com>,
Kees Cook <keescook@chromium.org>,
John Johansen <john.johansen@canonical.com>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, Jann Horn <jannh@google.com>
Subject: Re: [PATCH] security: fix integer overflow in lsm_set_self_attr() syscall
Date: Wed, 14 Feb 2024 13:53:13 -0500 [thread overview]
Message-ID: <1e24f1ef83614516c995e1cceccba6ff@paul-moore.com> (raw)
In-Reply-To: <20240214160538.1086089-1-jannh@google.com>
On Feb 14, 2024 Jann Horn <jannh@google.com> wrote:
>
> security_setselfattr() has an integer overflow bug that leads to
> out-of-bounds access when userspace provides bogus input:
> `lctx->ctx_len + sizeof(*lctx)` is checked against `lctx->len` (and,
> redundantly, also against `size`), but there are no checks on
> `lctx->ctx_len`.
> Therefore, userspace can provide an `lsm_ctx` with `->ctx_len` set to a
> value between `-sizeof(struct lsm_ctx)` and -1, and this bogus `->ctx_len`
> will then be passed to an LSM module as a buffer length, causing LSM
> modules to perform out-of-bounds accesses.
>
> The following reproducer will demonstrate this under ASAN (if AppArmor is
> loaded as an LSM):
> ```
> #define _GNU_SOURCE
> #include <unistd.h>
> #include <stdint.h>
> #include <stdlib.h>
> #include <sys/syscall.h>
>
> struct lsm_ctx {
> uint64_t id;
> uint64_t flags;
> uint64_t len;
> uint64_t ctx_len;
> char ctx[];
> };
>
> int main(void) {
> size_t size = sizeof(struct lsm_ctx);
> struct lsm_ctx *ctx = malloc(size);
> ctx->id = 104/*LSM_ID_APPARMOR*/;
> ctx->flags = 0;
> ctx->len = size;
> ctx->ctx_len = -sizeof(struct lsm_ctx);
> syscall(
> 460/*__NR_lsm_set_self_attr*/,
> /*attr=*/ 100/*LSM_ATTR_CURRENT*/,
> /*ctx=*/ ctx,
> /*size=*/ size,
> /*flags=*/ 0
> );
> }
> ```
>
> (I'm including an ASAN splat in the patch notes sent to the list.)
>
> Fixes: a04a1198088a ("LSM: syscalls for current process attributes")
> Signed-off-by: Jann Horn <jannh@google.com>
> Acked-by: Casey Schaufler <casey@schaufler-ca.com>
Looks good to me, thanks Jann. I'm going to merge this into
lsm/stable-6.8 and send this up to Linus soon (likely tomorrow).
--
paul-moore.com
next prev parent reply other threads:[~2024-02-14 18:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 16:05 [PATCH] security: fix integer overflow in lsm_set_self_attr() syscall Jann Horn
2024-02-14 16:53 ` Casey Schaufler
2024-02-15 0:45 ` Kees Cook
2024-02-15 13:02 ` Paul Moore
2024-02-14 18:53 ` Paul Moore [this message]
2024-02-14 23:24 ` Kees Cook
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=1e24f1ef83614516c995e1cceccba6ff@paul-moore.com \
--to=paul@paul-moore.com \
--cc=casey@schaufler-ca.com \
--cc=jannh@google.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.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).