linux-kernel - Re: [PATCH] x86/microcode/amd: fix uninitalized structure cp

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: <c7a44047-4d04-05aa-1734-97b4e368d839@canonical.com>
Date:   Thu, 16 Jan 2020 09:44:11 +0000
From:   Colin Ian King <colin.king@...onical.com>
To:     Borislav Petkov <bp@...en8.de>,
        Dan Carpenter <dan.carpenter@...cle.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        "H . Peter Anvin" <hpa@...or.com>, x86@...nel.org,
        kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/microcode/amd: fix uninitalized structure cp

On 15/01/2020 12:42, Borislav Petkov wrote:
> On Wed, Jan 15, 2020 at 07:25:07AM +0300, Dan Carpenter wrote:
>> It's probably complaining that cp.name[] isn't initialized.
> 
> That is possible.
> 
>> UBSan will probably generate a warning at runtime when we do:
>>
>> 	*ret = cp;
>>
>> But otherwise it's harmless.
> 
> Yes, because we don't do anything with cpio_data.name.
> 
Yep, apologies for the noise generated by this patch, please ignore it.

Colin