linux-kernel - Re: [PATCH] x86/sev: Fix __reserved field in sev

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <dcfc9264-959a-3bb5-95ad-548a6f019430@amd.com>
Date: Mon, 29 Jul 2024 18:45:21 -0500
From: "Paluri, PavanKumar" <papaluri@....com>
To: Borislav Petkov <bp@...en8.de>
Cc: linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
 Ingo Molnar <mingo@...hat.com>, Dave Hansen <dave.hansen@...ux.intel.com>,
 Tom Lendacky <thomas.lendacky@....com>, Ashish Kalra <ashish.kalra@....com>,
 Michael Roth <michael.roth@....com>, stable@...r.kernel.org
Subject: Re: [PATCH] x86/sev: Fix __reserved field in sev_config

Hi Boris,

On 7/29/2024 2:32 PM, Borislav Petkov wrote:
> On Mon, Jul 29, 2024 at 01:08:08PM -0500, Pavan Kumar Paluri wrote:
>> sev_config currently has debug, ghcbs_initialized, and use_cas fields.
>> However, __reserved count has not been updated. Fix this.
>>
>> Fixes: 34ff65901735 ("x86/sev: Use kernel provided SVSM Calling Areas")
>> Cc: stable@...r.kernel.org
> 
> stable because?
> 

Thanks for noticing this.

I shall remove Cc tag since:
1. The commit that introduced the bug is only part of 6.11-rc1. So there
is no stable kernel fix needed here.
2. An incorrect __reserved field did not cause any hang/data corruption
or a build-error.

I will re-spin a v2.

Thanks,
Pavan
>