From: Rusty Russell <rusty@rustcorp.com.au>
To: Kees Cook <keescook@chromium.org>, linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>,
Jani Nikula <jani.nikula@intel.com>,
Hannes Reinecke <hare@suse.de>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH] param: do not set store func without write perm
Date: Fri, 12 Dec 2014 13:38:08 +1030 [thread overview]
Message-ID: <87r3w5d0pz.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20141211222144.GA7070@www.outflux.net>
Kees Cook <keescook@chromium.org> writes:
> When a module_param is defined without DAC write permissions, it can
> still be changed at runtime and updated. Drivers using a 0444 permission
> may be surprised that these values can still be changed.
>
> For drivers that want to allow updates, any S_IW* flag will set the
> "store" function as before. Drivers without S_IW* flags will have the
> "store" function unset, unforcing a read-only value. Drivers that wish
> neither "store" nor "get" can continue to use "0" for perms to stay out
> of sysfs entirely.
Hmm, fair enough. The use of the acronym DAC here is a bit weird;
I would have just said:
/* If no perms, it's not writable even if root chmods it! */
if ((kp->perm & (S_IWUSR | S_IWGRP | S_IWOTH)) != 0)
new->attrs[num].mattr.store = param_attr_store;
Applied (with fuzz fixed, since I reworked that code in my tree).
Thanks,
Rusty.
>
> Old behavior:
> # cd /sys/module/snd/parameters
> # ls -l
> total 0
> -r--r--r-- 1 root root 4096 Dec 11 13:55 cards_limit
> -r--r--r-- 1 root root 4096 Dec 11 13:55 major
> -r--r--r-- 1 root root 4096 Dec 11 13:55 slots
> # cat major
> 116
> # echo -1 > major
> -bash: major: Permission denied
> # chmod u+w major
> # echo -1 > major
> # cat major
> -1
>
> New behavior:
> ...
> # chmod u+w major
> # echo -1 > major
> -bash: echo: write error: Input/output error
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> kernel/params.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/params.c b/kernel/params.c
> index db97b791390f..fd50ce9f1bbf 100644
> --- a/kernel/params.c
> +++ b/kernel/params.c
> @@ -647,7 +647,9 @@ static __modinit int add_sysfs_param(struct module_kobject *mk,
> sysfs_attr_init(&new->attrs[num].mattr.attr);
> new->attrs[num].param = kp;
> new->attrs[num].mattr.show = param_attr_show;
> - new->attrs[num].mattr.store = param_attr_store;
> + /* Do not allow runtime DAC changes to make param writable. */
> + if ((kp->perm & (S_IWUSR | S_IWGRP | S_IWOTH)) != 0)
> + new->attrs[num].mattr.store = param_attr_store;
> new->attrs[num].mattr.attr.name = (char *)name;
> new->attrs[num].mattr.attr.mode = kp->perm;
> new->num = num+1;
> --
> 1.9.1
>
>
> --
> Kees Cook
> Chrome OS Security
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2014-12-12 4:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 22:21 [PATCH] param: do not set store func without write perm Kees Cook
2014-12-12 3:08 ` Rusty Russell [this message]
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=87r3w5d0pz.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=geert@linux-m68k.org \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=jani.nikula@intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@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