linux-kernel - Re: [PATCH v2] powerpc/kexec: fix physical address calculation in clear_utlb

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: <174192385438.14370.6065221233235431919.b4-ty@linux.ibm.com>
Date: Fri, 14 Mar 2025 09:16:56 +0530
From: Madhavan Srinivasan <maddy@...ux.ibm.com>
To: Michael Ellerman <mpe@...erman.id.au>, Nicholas Piggin <npiggin@...il.com>,
        Naveen N Rao <naveen@...nel.org>,
        Christophe Leroy <christophe.leroy@...roup.eu>
Cc: linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org
Subject: Re: [PATCH v2] powerpc/kexec: fix physical address calculation in clear_utlb_entry()

On Thu, 06 Mar 2025 11:24:28 +0100, Christophe Leroy wrote:
> In relocate_32.S, function clear_utlb_entry() goes into real mode. To
> do so, it has to calculate the physical address based on the virtual
> address. To get the virtual address it uses 'bl' which is problematic
> (see commit c974809a26a1 ("powerpc/vdso: Avoid link stack corruption
> in __get_datapage()")). In addition, the calculation is done on a
> wrong address because 'bl' loads LR with the address of the following
> instruction, not the address of the target. So when the target is not
> the instruction following the 'bl' instruction, it may lead to
> unexpected behaviour.
> 
> [...]

Applied to powerpc/next.

[1/1] powerpc/kexec: fix physical address calculation in clear_utlb_entry()
      https://git.kernel.org/powerpc/c/861efb8a48ee8b73ae4e8817509cd4e82fd52bc4

Thanks