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]
Date: Thu, 18 Jan 2024 12:02:25 +0000
From: Will Deacon <will@...nel.org>
To: Mark Brown <broonie@...nel.org>,
	Catalin Marinas <catalin.marinas@....com>
Cc: kernel-team@...roid.com,
	Will Deacon <will@...nel.org>,
	stable@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org,
	Dave Martin <dave.martin@....com>
Subject: Re: [PATCH] arm64/sme: Always exit sme_alloc() early with existing storage

On Mon, 15 Jan 2024 20:15:46 +0000, Mark Brown wrote:
> When sme_alloc() is called with existing storage and we are not flushing we
> will always allocate new storage, both leaking the existing storage and
> corrupting the state. Fix this by separating the checks for flushing and
> for existing storage as we do for SVE.
> 
> Callers that reallocate (eg, due to changing the vector length) should
> call sme_free() themselves.
> 
> [...]

Applied to arm64 (for-next/core), thanks!

[1/1] arm64/sme: Always exit sme_alloc() early with existing storage
      https://git.kernel.org/arm64/c/dc7eb8755797

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ