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] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180116154630.ke53suvokynj73qd@gmail.com>
Date:   Tue, 16 Jan 2018 16:46:30 +0100
From:   Ingo Molnar <mingo@...nel.org>
To:     Juergen Gross <jgross@...e.com>
Cc:     linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
        x86@...nel.org, lenb@...nel.org, rafael.j.wysocki@...el.com,
        hpa@...or.com, tglx@...utronix.de, mingo@...hat.com
Subject: Re: [PATCH] x86/acpi: check rsdp address received via bootparams to
 be valid


* Juergen Gross <jgross@...e.com> wrote:

> There seem to exist several grub2 versions trashing
> boot_params.hdr.acpi_rsdp_addr.
> 
> So don't just believe this address to be valid, but verify it pointing
> to a valid RSDP table.

Exactly what kind of values do those Grub2 versions put into that field? Pointer 
to something, or random noise?

Also, what exactly does 'validation' mean, how robustly does it filter out of spec 
uses of the boot protocol?

Thanks,

	Ingo

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ