Received: by 10.213.65.68 with SMTP id h4csp2085431imn; Mon, 2 Apr 2018 00:17:49 -0700 (PDT) X-Google-Smtp-Source: AIpwx49mEdCXvKtAkd7TbFMA5djpywR81rEnu6IggNgfJvwnndqZvzitcM0+LApA0wTp0Ai1B5FN X-Received: by 2002:a17:902:d81:: with SMTP id 1-v6mr8588753plv.324.1522653468913; Mon, 02 Apr 2018 00:17:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522653468; cv=none; d=google.com; s=arc-20160816; b=cSNKTGl1sxCBptVBXKbvzK+ni4AZ/Dc9mZIPG4e5AExOoQVcjRLdSpIv0f1uCwd+R8 UZXPNBSvJdJngvC/0NY/MJPKUlPH7R9JrzfR6JENP303/aK23Uq7k0gJ2f5E51htvIn4 e8ffhi3b1upFAVRu1/h7a9jsNXWJs187MwPwzTgc79LtdD3o4dN5N6FwAm51pXeWSxDK aEwRSHvvq7ZzNPR0nP8ctFOWvGPbooOD0n4UzAwquFKXxFo/P3MyZM1arQb2VkKkdeZN dHTsg/yRtEndR/AxgTV9yej1BBKUcGZV7kY4uLssJACqz1b310o0F/suP/YF6N68Xheo nfzQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from :arc-authentication-results; bh=yFoJxkaOtofxUGutQMMSU7/lgVv7QCe/AWZoJYHr8Qs=; b=LmZOiwyEUX43FF7SlQz4SGpJYTjnYgufIg4GmNwZrHv/9Q5GYPnvAlQpo+2x7PBu8j btPWOvGtvwxVsubju7lx48GpoOsVwrDD8Rfd/tTXwYscBZYzCL5iYafc7yDagPvTXKq7 45KEHHA5F4YshpMAnq9UFFkZHY7fZOaN3n6PswrrzvnYMRHCHZ3r1Ih9lWAH9Rr9zGB+ 6he8C15AlboydFlKiUwtLo77H4/6ZvZmzLESxuBfbHIrnxzqSA2ug8ypmP9TyPXvfYPc HMOrPktP1EjpRIeYe2e5rPOiCd2mWkeoKXI4TrZ/KX4G2qN3yus2Ml4QE5pBDFmRHOSf jvlw== 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 bc11-v6si13636096plb.43.2018.04.02.00.17.35; Mon, 02 Apr 2018 00:17:48 -0700 (PDT) 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 S1754231AbeDBHQa (ORCPT + 99 others); Mon, 2 Apr 2018 03:16:30 -0400 Received: from mx2.suse.de ([195.135.220.15]:56334 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754114AbeDBHQ3 (ORCPT ); Mon, 2 Apr 2018 03:16:29 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id B3EFCAE16; Mon, 2 Apr 2018 07:16:27 +0000 (UTC) From: Takashi Iwai To: Bjorn Helgaas Cc: linux-kernel@vger.kernel.org, Michael Henders , Ram Pai Subject: [PATCH] resource: Fix integer overflow at reallocation Date: Mon, 2 Apr 2018 09:16:16 +0200 Message-Id: <20180402071616.27177-1-tiwai@suse.de> X-Mailer: git-send-email 2.16.2 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org We've got a bug report indicating a kernel panic at booting on an x86-32 system, and it turned out to be the invalid resource assigned after reallocation. __find_resource() first aligns the resource start address and resets the end address with start+size-1 accordingly, then checks whether it's contained. Here the end address may overflow the integer, although resource_contains() still returns true because the function validates only start and end address. So this ends up with returning an invalid resource (start > end). There was already an attempt to cover such a problem in the commit 47ea91b4052d ("Resource: fix wrong resource window calculation"), but this case is an overseen one. This patch adds the validity check of the newly calculated resource for avoiding the integer overflow problem. Bugzilla: http://bugzilla.opensuse.org/show_bug.cgi?id=1086739 Fixes: 23c570a67448 ("resource: ability to resize an allocated resource") Reported-and-tested-by: Michael Henders Cc: Signed-off-by: Takashi Iwai --- Bjorn, I send this to you since the bug hits during PCI init, although the culprit is in generic resource management. kernel/resource.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/kernel/resource.c b/kernel/resource.c index e270b5048988..2af6c03858b9 100644 --- a/kernel/resource.c +++ b/kernel/resource.c @@ -651,7 +651,8 @@ static int __find_resource(struct resource *root, struct resource *old, alloc.start = constraint->alignf(constraint->alignf_data, &avail, size, constraint->align); alloc.end = alloc.start + size - 1; - if (resource_contains(&avail, &alloc)) { + if (alloc.start <= alloc.end && + resource_contains(&avail, &alloc)) { new->start = alloc.start; new->end = alloc.end; return 0; -- 2.16.2