CVE-2026-80571: powerpc/pseries: papr-phy-attest - validate cmd.length, plug mem leak

CVE-2026-80571: powerpc/pseries: papr-phy-attest - validate cmd.length, plug mem leak

[Greg Kroah-Hartman]

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

powerpc/pseries: papr-phy-attest - validate cmd.length, plug mem leak

In papr_phy_attest_create_handle(), the params->cmd.length is not
validated before use, which can result in a buffer overlow.  Check it and
return -EINVAL if it is either 0 or exceeds sizeof(params->cmd).

Also, params is freed on the success path but not error. Free it on
errors after memory allocation.  And free it on negative fd.

The Linux kernel CVE team has assigned CVE-2026-80571 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.16 with commit 86900ab620a42396a749b506d4a187820fc3fabe and fixed in 6.18.46 with commit 828a8d1a9107aec6353d896882df8383accf7e80
	Issue introduced in 6.16 with commit 86900ab620a42396a749b506d4a187820fc3fabe and fixed in 7.1.10 with commit ed98ce338f9a65c90cb930b088f1eb36de7181af
	Issue introduced in 6.16 with commit 86900ab620a42396a749b506d4a187820fc3fabe and fixed in 7.2 with commit 5b17f3f34391372faf03e79d947e0c50ab6dd258

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-80571
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	arch/powerpc/platforms/pseries/papr-phy-attest.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/828a8d1a9107aec6353d896882df8383accf7e80
	https://git.kernel.org/stable/c/ed98ce338f9a65c90cb930b088f1eb36de7181af
	https://git.kernel.org/stable/c/5b17f3f34391372faf03e79d947e0c50ab6dd258