linux-kernel - Re: [PATCH] Lock down drivers that can have io ports, io mem, irqs and dma changed

lists.openwall.net		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 linux-cve-announce 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, 24 Nov 2016 17:34:45 +0000
From:   David Howells <dhowells@...hat.com>
To:     Dominik Brodowski <linux@...inikbrodowski.net>
Cc:     dhowells@...hat.com, keyrings@...r.kernel.org,
        matthew.garrett@...ula.com, linux-security-module@...r.kernel.org,
        linux-efi@...r.kernel.org, linux-kernel@...r.kernel.org,
        gnomes@...rguk.ukuu.org.uk
Subject: Re: [PATCH] Lock down drivers that can have io ports, io mem, irqs and dma changed

Dominik Brodowski <linux@...inikbrodowski.net> wrote:

> > > 	- Abort in drivers/pcmcia/cistpl.c::pccard_store_cis() or remove
> > > 	  write access to the "cis" file in
> > > 	  drivers/pcmcia/cistpl.c::pccard_cis_attr
> > 
> > What is that doing?  Allowing the device to be reconfigured?
> 
> Exactly. It is a different interface for updating the firmware -- which
> includes ioports etc. In theory, any access should be limited to areas which
> are registered to the bridge devices. But you never know...

Ah, I see.  Should this be using request_firmware()?

David