From: serge@hallyn.com (Serge E. Hallyn)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] cap_inode_getsecurity: use d_find_any_alias() instead of d_find_alias()
Date: Thu, 28 Jun 2018 10:01:52 -0500 [thread overview]
Message-ID: <20180628150152.GA10398@mail.hallyn.com> (raw)
In-Reply-To: <1530082758.30361.7.camel@mtkswgap22>
Quoting Eddie.Horng (eddie.horng at mediatek.com):
>
> The code in cap_inode_getsecurity(), introduced by commit 8db6c34f1dbc
> ("Introduce v3 namespaced file capabilities"), should use
> d_find_any_alias()
> instead of d_find_alias() do handle unhashed dentry correctly. This is
> needed,
> for example, if execveat() is called with an open but unlinked overlayfs
> file, because overlayfs unhashes dentry on unlink.
>
> Below reproducer and setup can reproduce the case.
> const char* exec="echo";
> const char *newargv[] = { "echo", "hello", NULL};
> const char *newenviron[] = { NULL };
> int fd, err;
>
> fd = open(exec, O_PATH);
> unlink(exec);
> err = syscall(322/*SYS_execveat*/, fd, "", newargv, newenviron,
> AT_EMPTY_PATH);
> if(err<0)
> fprintf(stderr, "execveat: %s\n", strerror(errno));
>
> gcc compile into ~/test/a.out
> mount -t overlay -orw,lowerdir=/mnt/l,upperdir=/mnt/u,workdir=/mnt/w
> none /mnt/m
> cd /mnt/m
> cp /bin/echo .
> ~/test/a.out
>
> Expected result:
> hello
> Actually result:
> execveat: Invalid argument
> dmesg:
> Invalid argument reading file caps for /dev/fd/3
>
> Suggested-by: Amir Goldstein <amir73il@gmail.com>
> Fixes: 8db6c34f1dbc ("Introduce v3 namespaced file capabilities")
Did 8db6c34f1dbc actually introduce a regression?
Note this does seem to potentially introduce an attack where a
user fetches an open fd to any file with filecaps, waits for a
CVE publication, then after the admin has updated the package
causing the file to be deleted, then does execveat to run the
deleted package with privs.
> Signed-off-by: Eddie Horng <eddie.horng@mediatek.com>
> ---
> security/commoncap.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/security/commoncap.c b/security/commoncap.c
> index 1ce701fcb3f3..147f6131842a 100644
> --- a/security/commoncap.c
> +++ b/security/commoncap.c
> @@ -388,7 +388,7 @@ int cap_inode_getsecurity(struct inode *inode, const
> char *name, void **buffer,
> if (strcmp(name, "capability") != 0)
> return -EOPNOTSUPP;
>
> - dentry = d_find_alias(inode);
> + dentry = d_find_any_alias(inode);
> if (!dentry)
> return -EINVAL;
>
> --
> 2.12.5
>
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-06-28 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1530082758.30361.7.camel@mtkswgap22>
2018-06-27 8:18 ` [PATCH] cap_inode_getsecurity: use d_find_any_alias() instead of d_find_alias() Amir Goldstein
2018-06-28 15:01 ` Serge E. Hallyn [this message]
2018-06-28 16:54 ` Amir Goldstein
2018-06-28 17:26 ` Serge E. Hallyn
2018-06-28 17:57 ` Amir Goldstein
2018-06-28 18:28 ` Serge E. Hallyn
[not found] ` <1530237431.30361.29.camel@mtkswgap22>
2018-06-29 2:53 ` Serge E. Hallyn
2018-07-03 8:09 ` Amir Goldstein
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=20180628150152.GA10398@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=linux-security-module@vger.kernel.org \
/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).