asus-wmi: Restrict debugfs interface when the kernel is locked down
authorMatthew Garrett <matthew.garrett@nebula.com>
Wed, 5 Apr 2017 16:40:30 +0000 (17:40 +0100)
committerPeter Michael Green <plugwash@raspbian.org>
Wed, 7 Feb 2018 23:32:32 +0000 (23:32 +0000)
commit76377e4b9f578331e102b444f0e29f42b03cc99f
treeb4ee64713e25718df4ca54e0274cdc586073abb5
parent41aeb8fde92dd39105a93e34d6b4d04cde039002
asus-wmi: Restrict debugfs interface when the kernel is locked down

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.

Signed-off-by: Matthew Garrett <matthew.garrett@nebula.com>
Signed-off-by: David Howells <dhowells@redhat.com>
Gbp-Pq: Topic features/all/lockdown
Gbp-Pq: Name 0052-asus-wmi-Restrict-debugfs-interface-when-the-kernel-.patch
drivers/platform/x86/asus-wmi.c