linux-kernel - Re: [PATCH V3 03/11] x86: Lock down IO port access when module security is enabled

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]

Message-ID: <5227FFE8.5050102@zytor.com>
Date:	Wed, 04 Sep 2013 20:52:08 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Matthew Garrett <matthew.garrett@...ula.com>
CC:	linux-kernel@...r.kernel.org, linux-efi@...r.kernel.org,
	keescook@...omium.org
Subject: Re: [PATCH V3 03/11] x86: Lock down IO port access when module security
 is enabled

On 09/03/2013 04:50 PM, Matthew Garrett wrote:
> IO port access would permit users to gain access to PCI configuration
> registers, which in turn (on a lot of hardware) give access to MMIO register
> space. This would potentially permit root to trigger arbitrary DMA, so lock
> it down by default.
> 
> Signed-off-by: Matthew Garrett <matthew.garrett@...ula.com>

Seriously... just deny CAP_SYS_RAWIO to any system in secure mode.

	-hpa


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/