linux-hardening - Re: [PATCH v2 0/4] KVM: arm64: UBSAN at EL2

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: <202505080929.95B2310@keescook>
Date: Thu, 8 May 2025 09:29:50 -0700
From: Kees Cook <kees@...nel.org>
To: Marc Zyngier <maz@...nel.org>
Cc: Mostafa Saleh <smostafa@...gle.com>, kvmarm@...ts.linux.dev,
	kasan-dev@...glegroups.com, linux-hardening@...r.kernel.org,
	linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, will@...nel.org,
	oliver.upton@...ux.dev, broonie@...nel.org, catalin.marinas@....com,
	tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
	dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com,
	elver@...gle.com, andreyknvl@...il.com, ryabinin.a.a@...il.com,
	akpm@...ux-foundation.org, yuzenghui@...wei.com,
	suzuki.poulose@....com, joey.gouly@....com, masahiroy@...nel.org,
	nathan@...nel.org, nicolas.schier@...ux.dev
Subject: Re: [PATCH v2 0/4] KVM: arm64: UBSAN at EL2

On Wed, May 07, 2025 at 11:35:38AM +0100, Marc Zyngier wrote:
> On Wed, 30 Apr 2025 19:32:23 +0100,
> Kees Cook <kees@...nel.org> wrote:
> > 
> > On Wed, Apr 30, 2025 at 04:27:07PM +0000, Mostafa Saleh wrote:
> > > Many of the sanitizers the kernel supports are disabled when running
> > > in EL2 with nvhe/hvhe/proctected modes, some of those are easier
> > > (and makes more sense) to integrate than others.
> > > Last year, kCFI support was added in [1]
> > > 
> > > This patchset adds support for UBSAN in EL2.
> > 
> > This touches both UBSAN and arm64 -- I'm happy to land this via the
> > hardening tree, but I expect the arm64 folks would rather take it via
> > their tree. What would people like to have happen?
> 
> FWIW, I have now taken this in kvmarm/next. A stable branch is
> available at [1] for anyone to pull and resolve potential conflicts.

Thanks!


-- 
Kees Cook