lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 13 Apr 2017 10:44:26 -0700
From:   Andy Lutomirski <>
Cc:     Darren Hart <>,
        Andrew Lutomirski <>,
        Michał Kępień <>,
        "Rafael J. Wysocki" <>,
        Len Brown <>,
        Pali Rohár <>,
        Corentin Chary <>,
        Andy Shevchenko <>,
        "" <>,,
        "" <>
Subject: Re: RFC: WMI Enhancements

On Thu, Apr 13, 2017 at 10:39 AM,  <> wrote:
>> -----Original Message-----
>> From: Darren Hart []
>> Sent: Thursday, April 13, 2017 12:06 PM
>> To: Limonciello, Mario <>
>> Cc:;;;
>>;; platform-
>> Subject: Re: RFC: WMI Enhancements

> Well the "most" interesting to me is the SMBIOS calling interface on the
> regular Dell GUID (WMBA IIRC).  That's what is used to manipulate keyboard
> LED timeouts in dell-laptop (although through direct SMI today).
> It's also what is used for other SMBIOS calls like changing random BIOS settings
> that shouldn't be generically exposed in sysfs but should be controlled by
> manageability tools.
> Example: turning on/off legacy option ROM or changing legacy boot order.

IIUC we basically can't expose the SMI--based interface to this entry
point to userspace because of its use of physical addressing.  It is
reasonably safe to expose the WMI version?  (IOW should be expect that
it doesn't enable kernel-mode or SMM code execution?)

TBH, I've occasionally considered writing a driver to expose SMM code
execution on systems with a known reliable exploit :)

Powered by blists - more mailing lists