Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2990715imu; Sun, 9 Dec 2018 14:28:27 -0800 (PST) X-Google-Smtp-Source: AFSGD/UkEp17dvU6YIdoSeFjvPv9v6tpYtq8Q3qhrnME/hE+wKaMrVUc9DIwQl8hQurtXV/IccHL X-Received: by 2002:a17:902:e085:: with SMTP id cb5mr9794599plb.24.1544394507734; Sun, 09 Dec 2018 14:28:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544394507; cv=none; d=google.com; s=arc-20160816; b=U4Qgq+baN7tHjzv+S0TNEk5dEAZU10aZ0cQXrexirDRkcU9GdB2i5uaY8YhbeEL49n tyMKeLp5DueqhOI/I57fFOOcIXjO7RORNkMnbKmJsFyDxWxDl98nwnYWsIxNH+D4WKEQ kSmyQ3H0396uT7h8UDL+TKaWELMe9TJSI7tfaKGvBruplHh8sYD0ZtfBgJLEpk+T+0sO pFygLnErcHuQWbmqjPv/kitOF6IFgeFFT32vCJW/BVHoUg4LZPz9mUxyK72mHJWLqWps 2Oi9VQR/lef6+Zksyo54E4bMybwSeLQsIT3ek7T1091/xLShpObqVKdK5A4WhprIZqI2 SLXw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:subject:message-id:date:cc:to :from:mime-version:content-transfer-encoding:content-disposition; bh=P/AXI73EgjmXOqIupn1a3SfdzSwCxBTmcrG6vnKf3LU=; b=CDT+HYVp97J6e6shhm4rdA93dwiVB6KMsMNxKJTo7NM6z6QeIFmchMxiVt11reGFS2 ZSn/h+YQlCBDyXnoPyr1qTQHTF1u1UWpYgs1WaC0HEhwDheSOHMBFqGczcd04jGdYLco Ew4yE5UxbaR5k2i599BDeHaOhjggAUmzRAfZn4y0MUxJCrTB3Rmxo9tV/yYy/i4f/uMu d4KHvrfxUfSynx+OLINmMO6stjElnHN23792whw2faMG5iXjZo9NkuqT/uc55zYTHhU9 hThApF5NkysLcep2Rt4F/1YB8IEzpX/BmGr+6uO8prRVwz7ZVqlG+oxsgtRo+GK9q4oY ZW4Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h69si8074052pge.121.2018.12.09.14.28.12; Sun, 09 Dec 2018 14:28:27 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726304AbeLIVzM (ORCPT + 99 others); Sun, 9 Dec 2018 16:55:12 -0500 Received: from shadbolt.e.decadent.org.uk ([88.96.1.126]:34542 "EHLO shadbolt.e.decadent.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726309AbeLIVzJ (ORCPT ); Sun, 9 Dec 2018 16:55:09 -0500 Received: from pub.yeoldevic.com ([81.174.156.145] helo=deadeye) by shadbolt.decadent.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1gW72Y-0002iq-VW; Sun, 09 Dec 2018 21:55:07 +0000 Received: from ben by deadeye with local (Exim 4.91) (envelope-from ) id 1gW72Y-0003DX-C7; Sun, 09 Dec 2018 21:55:06 +0000 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 From: Ben Hutchings To: linux-kernel@vger.kernel.org, stable@vger.kernel.org CC: akpm@linux-foundation.org, "Thomas Gleixner" , "Team OWL337" , "John Stultz" Date: Sun, 09 Dec 2018 21:50:33 +0000 Message-ID: X-Mailer: LinuxStableQueue (scripts by bwh) X-Patchwork-Hint: ignore Subject: [PATCH 3.16 018/328] alarmtimer: Prevent overflow for relative nanosleep In-Reply-To: X-SA-Exim-Connect-IP: 81.174.156.145 X-SA-Exim-Mail-From: ben@decadent.org.uk X-SA-Exim-Scanned: No (on shadbolt.decadent.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 3.16.62-rc1 review patch. If anyone has any objections, please let me know. ------------------ From: Thomas Gleixner commit 5f936e19cc0ef97dbe3a56e9498922ad5ba1edef upstream. Air Icy reported: UBSAN: Undefined behaviour in kernel/time/alarmtimer.c:811:7 signed integer overflow: 1529859276030040771 + 9223372036854775807 cannot be represented in type 'long long int' Call Trace: alarm_timer_nsleep+0x44c/0x510 kernel/time/alarmtimer.c:811 __do_sys_clock_nanosleep kernel/time/posix-timers.c:1235 [inline] __se_sys_clock_nanosleep kernel/time/posix-timers.c:1213 [inline] __x64_sys_clock_nanosleep+0x326/0x4e0 kernel/time/posix-timers.c:1213 do_syscall_64+0xb8/0x3a0 arch/x86/entry/common.c:290 alarm_timer_nsleep() uses ktime_add() to add the current time and the relative expiry value. ktime_add() has no sanity checks so the addition can overflow when the relative timeout is large enough. Use ktime_add_safe() which has the necessary sanity checks in place and limits the result to the valid range. Fixes: 9a7adcf5c6de ("timers: Posix interface for alarm-timers") Reported-by: Team OWL337 Signed-off-by: Thomas Gleixner Cc: John Stultz Link: https://lkml.kernel.org/r/alpine.DEB.2.21.1807020926360.1595@nanos.tec.linutronix.de Signed-off-by: Ben Hutchings --- kernel/time/alarmtimer.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) --- a/kernel/time/alarmtimer.c +++ b/kernel/time/alarmtimer.c @@ -775,7 +775,8 @@ static int alarm_timer_nsleep(const cloc /* Convert (if necessary) to absolute time */ if (flags != TIMER_ABSTIME) { ktime_t now = alarm_bases[type].gettime(); - exp = ktime_add(now, exp); + + exp = ktime_add_safe(now, exp); } if (alarmtimer_do_nsleep(&alarm, exp))