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
| ||
|
Message-Id: <20170831154215.520853490@linuxfoundation.org> Date: Thu, 31 Aug 2017 17:44:03 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-kernel@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, stable@...r.kernel.org, Catalin Marinas <catalin.marinas@....com>, Laura Abbott <labbott@...hat.com>, Steve Capper <steve.capper@....com>, James Morse <james.morse@....com>, Mark Rutland <mark.rutland@....com>, Will Deacon <will.deacon@....com> Subject: [PATCH 4.4 10/16] arm64: mm: abort uaccess retries upon fatal signal 4.4-stable review patch. If anyone has any objections, please let me know. ------------------ From: Mark Rutland <mark.rutland@....com> commit 289d07a2dc6c6b6f3e4b8a62669320d99dbe6c3d upstream. When there's a fatal signal pending, arm64's do_page_fault() implementation returns 0. The intent is that we'll return to the faulting userspace instruction, delivering the signal on the way. However, if we take a fatal signal during fixing up a uaccess, this results in a return to the faulting kernel instruction, which will be instantly retried, resulting in the same fault being taken forever. As the task never reaches userspace, the signal is not delivered, and the task is left unkillable. While the task is stuck in this state, it can inhibit the forward progress of the system. To avoid this, we must ensure that when a fatal signal is pending, we apply any necessary fixup for a faulting kernel instruction. Thus we will return to an error path, and it is up to that code to make forward progress towards delivering the fatal signal. Cc: Catalin Marinas <catalin.marinas@....com> Cc: Laura Abbott <labbott@...hat.com> Reviewed-by: Steve Capper <steve.capper@....com> Tested-by: Steve Capper <steve.capper@....com> Reviewed-by: James Morse <james.morse@....com> Tested-by: James Morse <james.morse@....com> Signed-off-by: Mark Rutland <mark.rutland@....com> Signed-off-by: Will Deacon <will.deacon@....com> Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org> --- arch/arm64/mm/fault.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) --- a/arch/arm64/mm/fault.c +++ b/arch/arm64/mm/fault.c @@ -313,8 +313,11 @@ retry: * signal first. We do not need to release the mmap_sem because it * would already be released in __lock_page_or_retry in mm/filemap.c. */ - if ((fault & VM_FAULT_RETRY) && fatal_signal_pending(current)) + if ((fault & VM_FAULT_RETRY) && fatal_signal_pending(current)) { + if (!user_mode(regs)) + goto no_context; return 0; + } /* * Major/minor page fault accounting is only done on the initial
Powered by blists - more mailing lists