From: Casey Schaufler <casey@schaufler-ca.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: [PATCH 1/2] Smack: fix another vsscanf out of bounds
Date: Thu, 23 Jul 2020 09:38:28 -0700 [thread overview]
Message-ID: <a59e6bb4-91ef-db75-f91b-1329b073307d@schaufler-ca.com> (raw)
In-Reply-To: <20200723152219.GA302005@mwanda>
On 7/23/2020 8:22 AM, Dan Carpenter wrote:
> This is similar to commit 84e99e58e8d1 ("Smack: slab-out-of-bounds in
> vsscanf") where we added a bounds check on "rule".
>
> Reported-by: syzbot+a22c6092d003d6fe1122@syzkaller.appspotmail.com
> Fixes: f7112e6c9abf ("Smack: allow for significantly longer Smack labels v4")
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Thanks. I'll be testing these and take them assuming they pass.
> ---
> This check is very straight forward and should fix the bug. But if you
> look at the fixes tag we used to rely on the check:
>
> if (count != (SMK_CIPSOMIN + catlen * SMK_DIGITLEN))
>
> and now that has been changed to:
>
> if (format == SMK_FIXED24_FMT &&
> count != (SMK_CIPSOMIN + catlen * SMK_DIGITLEN))
> goto out;
>
> so it doesn't apply for every format.
>
> security/smack/smackfs.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/security/smack/smackfs.c b/security/smack/smackfs.c
> index c21b656b3263..81c6ceeaa4f9 100644
> --- a/security/smack/smackfs.c
> +++ b/security/smack/smackfs.c
> @@ -905,6 +905,10 @@ static ssize_t smk_set_cipso(struct file *file, const char __user *buf,
>
> for (i = 0; i < catlen; i++) {
> rule += SMK_DIGITLEN;
> + if (rule > data + count) {
> + rc = -EOVERFLOW;
> + goto out;
> + }
> ret = sscanf(rule, "%u", &cat);
> if (ret != 1 || cat > SMACK_CIPSO_MAXCATNUM)
> goto out;
next prev parent reply other threads:[~2020-07-23 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 18:32 KASAN: slab-out-of-bounds Read in vsscanf (2) syzbot
2020-07-23 15:22 ` [PATCH 1/2] Smack: fix another vsscanf out of bounds Dan Carpenter
2020-07-23 16:38 ` Casey Schaufler [this message]
2020-07-23 15:23 ` [PATCH 2/2] Smack: prevent underflow in smk_set_cipso() Dan Carpenter
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=a59e6bb4-91ef-db75-f91b-1329b073307d@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=dan.carpenter@oracle.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=syzkaller-bugs@googlegroups.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
all inboxes | Powered by JetHome®