From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mout02.posteo.de (mout02.posteo.de [185.67.36.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 63357322A for ; Sat, 4 Oct 2025 08:35:47 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.67.36.66 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1759566949; cv=none; b=bwvsT3yJ4QTZPHC/3/uKTvC7M6ENPwqSwjIup5EpeDjbdRX2NkLO0WwbaQvYuk88EA5LxQYKiiA52S74E4VQ2uCx11hvgBw77DibYUomC1YFkF1OQDH8NJkQVCzncGm0jZQKvBCLE9+fJQ9Ox8Btj6IEKVfLDJV+mBfiv2bQ4x4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1759566949; c=relaxed/simple; bh=t0S21gYyo7eRaP9+88S3WoJCHO6nkljYG7DExrHhjmc=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=lvt5nvmX17FX5kT8JURVP9vaLuOBoAEbzN2V7UPTnu4A/Pg5AA4+C8taB5AH2wiNtThRHrhCST2tzCnV8aNzWc5BWJsa+sxg7A37BROjJy1WeKp2iXfV/NOfXJ/tgswwwj9+f4bnKIRhDxQ+Se7JMx293H0SqM0CIgCKNMFX9N4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=posteo.de; spf=pass smtp.mailfrom=posteo.de; dkim=pass (2048-bit key) header.d=posteo.de header.i=@posteo.de header.b=YiFHVhgE; arc=none smtp.client-ip=185.67.36.66 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=posteo.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=posteo.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=posteo.de header.i=@posteo.de header.b="YiFHVhgE" Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id BFFC1240104 for ; Sat, 4 Oct 2025 10:35:40 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=posteo.de; s=2017; t=1759566940; bh=ojT6o3fqx9yoN4VZsVYxlr2GEiqB3WxDl+QSQ8TADVM=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:From:Content-Type: Content-Transfer-Encoding:From; b=YiFHVhgExP2vgmTMbCnSIeR1RJjnUVq/1dAhZJy1np5ty1D1Z+Gdl8mQsyJ9EAj+A UW9lePV0HZpFCf5D9sl31AnH9R4CLbVmX+A+ps/6J31rd7SLuwESfo4HFoSa4jYsWb ZN4LTd694y/LFCi0r2UU7VTnMfh6FGNdkHtMEUaAeQx41RBOxQmkksJHikJ1Pg2rPB zjGUp49GdOMO98G2HhtiR5+7cS8WU9SpoV6NOLSUt5F2R3sqjPQzLB7/3kOrYqqE3P YwFYo3k7B2xfb7nNlAHGmU/sT5uoW/ns2gr7mgHHEYW/NKWzDKUE0v4aj1lLBj5oDa d8FX6o5LnLikQ== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4cdzPl6YGHz6tm8; Sat, 4 Oct 2025 10:35:39 +0200 (CEST) Message-ID: <8ce2f56c-4fea-47e2-a0e2-9b24b66874ff@posteo.de> Date: Sat, 04 Oct 2025 08:35:40 +0000 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [PATCH] tpm: infineon: add bounds check in tpm_inf_recv To: Paul Menzel Cc: peterhuewe@gmx.de, jarkko@kernel.org, jgg@ziepe.ca, linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org References: <20251003092544.12118-1-shahriyar@posteo.de> Content-Language: en-US From: Shahriyar In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Dear Paul, > > Is it possible to enforce this situation to ensure your patch works? > Triggering the issue requires interposing the hardware or a MCU to emulate the TPM and send malformed TPM replies, I might be able to test this using Qemu, but that takes some time. For the rest of your suggestions, I'll send another patch. BR, /shj