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: <aOYBpY7jPx622xcz@infradead.org>
Date: Tue, 7 Oct 2025 23:16:05 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Kees Cook <kees@...nel.org>
Cc: Christian Brauner <brauner@...nel.org>,
	syzbot+a9391462075ffb9f77c6@...kaller.appspotmail.com,
	Sumit Semwal <sumit.semwal@...aro.org>,
	Christian König <christian.koenig@....com>,
	linux-media@...r.kernel.org, dri-devel@...ts.freedesktop.org,
	linaro-mm-sig@...ts.linaro.org, linux-kernel@...r.kernel.org,
	linux-hardening@...r.kernel.org
Subject: Re: [PATCH] dma-buf: use SB_I_NOEXEC and SB_I_NODEV

On Tue, Oct 07, 2025 at 11:10:32PM -0700, Kees Cook wrote:
> The dma-buf pseudo-filesystem should never have executable mappings nor
> device nodes. Set SB_I_NOEXEC and SB_I_NODEV on the superblock to enforce
> this at the filesystem level, similar to secretmem, commit 98f99394a104
> ("secretmem: use SB_I_NOEXEC").
> 
> Fix the syzbot-reported warning from the exec code to enforce this
> requirement:

Can you please just enforce this in init_pseudo?  If a file system
really wants to support devices or executable it can clear them,
but a quick grep suggests that none of them should.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ