linux-kernel - Re: [PATCH 1/3] mm: vmalloc: export __vmalloc_node

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

Message-ID: <ZqBaqlXi7zTjntP4@infradead.org>
Date: Tue, 23 Jul 2024 18:36:42 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Matthew Wilcox <willy@...radead.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
	Mary Strodl <mstrodl@...edom.csh.rit.edu>,
	Christian Gmeiner <christian.gmeiner@...il.com>,
	Christoph Hellwig <hch@...radead.org>,
	Mary Strodl <mstrodl@....rit.edu>, linux-kernel@...r.kernel.org,
	urezki@...il.com, linux-mm@...ck.org, lee@...nel.org,
	andi.shyti@...nel.org, linux-i2c@...r.kernel.org,
	s.hauer@...gutronix.de
Subject: Re: [PATCH 1/3] mm: vmalloc: export __vmalloc_node_range

On Wed, Jul 24, 2024 at 01:16:02AM +0100, Matthew Wilcox wrote:
> That we're running arbitrary x86 code (provided by the manufacturer)
> inside the kernel where it can undermine every security guarantee we
> provide?

.. and by exporting the interface allow arbitrary other code including
exploit code to allocate writable and executable memory?