Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp3928459pxj; Mon, 21 Jun 2021 09:34:02 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzu7qjKyu3IYVwyOAUti+Be0hJVvAiF5TcSmJe9GJ625S3SEnYMgvj2Yyayp8RzKcDJB3B+ X-Received: by 2002:a05:6e02:511:: with SMTP id d17mr3156947ils.277.1624293242002; Mon, 21 Jun 2021 09:34:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624293241; cv=none; d=google.com; s=arc-20160816; b=hLw2GrR8KSgIBpjQ07dyAbj8A9BLngl/iODYZyYbxW4tdipgdZS8tPpSTD5CU60c7p GB1MdFL02O6WqZdfE5fUxakh2hIQdL8qYAPkRGazA31qXtDWPWc6+pHezujv7tfYmZ1T EYlUQ5zAiH3tEsRZFOyycj0WLPKhJNUPtTXjI4CjeUh4BlKWK3/Hh9DRO1gOShkYc0uA XX/GsCpSCYJQqHkwJzJwuWRvZ/0CLjtqNmgTujKptD218O3R77Qeg1H60vraHwODnL1/ YPqEHCAMu+GIjg2GmuLLwe+jreLMrdlZdo8m+dbbdmSaCjiVyGbxxqIyxrcC7/bNtfN5 7aRw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=psjugBR3iXkxM52DWy9rWKTtCb+YqxfekB2luRVaXso=; b=NtmaSkyp5cStWGPttNADMsfXV6yqdvbOW13/5m6LbN4IS5supJMCEOqs0ACcJsk8BZ yPS/SquA77tp+1o1pWfPOn/uZko/ckAArAPsDXAkz3tz0R67pEF5tyd0luPA/CiKYDcR xT/5bCW+Ze/t8YlLMLrs/cHFpXqZwCpMgF8rHjfXH8fcUSrPQDIJtOzd9Pr4PiCYiXo/ cKayzLdQP79PATq9o/6BMpone9iJaG2cFXeGCYuh/CtSOSK38DHpy/tU3/JWkfl5UXU8 /yqnqre3VSJd1ekZpKm5Ol+j81yJkFEZP7WBiYYRWKR1D1ww4npj5nIIeMLyoc+wvUkZ uUHw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=w61UCgDt; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h78si19938681iof.66.2021.06.21.09.33.49; Mon, 21 Jun 2021 09:34:01 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=w61UCgDt; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231321AbhFUQdg (ORCPT + 99 others); Mon, 21 Jun 2021 12:33:36 -0400 Received: from mail.kernel.org ([198.145.29.99]:48560 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231250AbhFUQaJ (ORCPT ); Mon, 21 Jun 2021 12:30:09 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 69848613E2; Mon, 21 Jun 2021 16:25:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1624292701; bh=gZsWYGD6DSZN9b0ieH25qpJfCk/qelBdQLh26Y8L3ug=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=w61UCgDteqPIOAs8CDyUK81O65yOj6+wFeDNGg4Wx66huns5tL4uHArbYb4GQEm7F HYdMhp1lzZ0dOKb/mrLEHxCxenBdgTz9O2qYGJNcgusBg2avKkYJTZX53DRVCf5nWO iTQdc7iRQxVO9LZ0LUaejHlnsAfxZtnlJqPYj/NM= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Norbert Slusarek , Oliver Hartkopp , Marc Kleine-Budde Subject: [PATCH 5.10 098/146] can: bcm: fix infoleak in struct bcm_msg_head Date: Mon, 21 Jun 2021 18:15:28 +0200 Message-Id: <20210621154917.425217456@linuxfoundation.org> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210621154911.244649123@linuxfoundation.org> References: <20210621154911.244649123@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Norbert Slusarek commit 5e87ddbe3942e27e939bdc02deb8579b0cbd8ecc upstream. On 64-bit systems, struct bcm_msg_head has an added padding of 4 bytes between struct members count and ival1. Even though all struct members are initialized, the 4-byte hole will contain data from the kernel stack. This patch zeroes out struct bcm_msg_head before usage, preventing infoleaks to userspace. Fixes: ffd980f976e7 ("[CAN]: Add broadcast manager (bcm) protocol") Link: https://lore.kernel.org/r/trinity-7c1b2e82-e34f-4885-8060-2cd7a13769ce-1623532166177@3c-app-gmx-bs52 Cc: linux-stable Signed-off-by: Norbert Slusarek Acked-by: Oliver Hartkopp Signed-off-by: Marc Kleine-Budde Signed-off-by: Greg Kroah-Hartman --- net/can/bcm.c | 3 +++ 1 file changed, 3 insertions(+) --- a/net/can/bcm.c +++ b/net/can/bcm.c @@ -402,6 +402,7 @@ static enum hrtimer_restart bcm_tx_timeo if (!op->count && (op->flags & TX_COUNTEVT)) { /* create notification to user */ + memset(&msg_head, 0, sizeof(msg_head)); msg_head.opcode = TX_EXPIRED; msg_head.flags = op->flags; msg_head.count = op->count; @@ -439,6 +440,7 @@ static void bcm_rx_changed(struct bcm_op /* this element is not throttled anymore */ data->flags &= (BCM_CAN_FLAGS_MASK|RX_RECV); + memset(&head, 0, sizeof(head)); head.opcode = RX_CHANGED; head.flags = op->flags; head.count = op->count; @@ -560,6 +562,7 @@ static enum hrtimer_restart bcm_rx_timeo } /* create notification to user */ + memset(&msg_head, 0, sizeof(msg_head)); msg_head.opcode = RX_TIMEOUT; msg_head.flags = op->flags; msg_head.count = op->count;