[PATCH 15/24] asus-wmi: Restrict debugfs interface when the kernel is locked down
David Howells
dhowells at redhat.com
Fri Apr 7 12:50:49 UTC 2017
Andy Shevchenko <andy.shevchenko at gmail.com> wrote:
> > From: Matthew Garrett <matthew.garrett at nebula.com>
> >
> > We have no way of validating what all of the Asus WMI methods do on a given
> > machine - and there's a risk that some will allow hardware state to be
> > manipulated in such a way that arbitrary code can be executed in the
> > kernel, circumventing module loading restrictions. Prevent that if the
> > kernel is locked down.
>
> > + if (kernel_is_locked_down())
> > + return -EPERM;
>
> It looks a bit fragile when responsility of whatever reasons kernel
> can't serve become a driver burden.
> Can we fix this in debugfs framework instead?
Fix it with debugfs how? We can't offload the decision to userspace.
David
--
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
More information about the Linux-security-module-archive
mailing list