linux-kernel - RFC: Tainting the kernel on raw I/O access

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-next>] [day] [month] [year] [list]

Date:	Wed, 03 Sep 2014 14:20:59 -0700
From:	"H. Peter Anvin" <h.peter.anvin@...el.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
CC:	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Matthew Garrett <mjg59@...f.ucam.org>
Subject: RFC: Tainting the kernel on raw I/O access

In a meeting earlier today, we discussed MSR access and that it could be
used to do bad things.  The same applies to other forms of raw I/O
(/dev/mem, /dev/port, ioperm, iopl, etc.)

This is basically the same problem with which the secure boot people
have been struggling.

Peter Z. suggested we should taint the kernel on raw I/O access, and I
tend to concur.

So what I would like to suggest is that we create a new kernel helper
function which can return an error in secure boot mode and otherwise
taints the kernel with a raw I/O taint.

What do people think?

	-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/