Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp764232imw; Fri, 8 Jul 2022 11:15:11 -0700 (PDT) X-Google-Smtp-Source: AGRyM1uJ4tAWBakdrJgk+hjyPPvzhxrLotB0pj452dXUqNIAEJE0is5nc+iYZ7t8xWVXEprbIctc X-Received: by 2002:a05:6402:2786:b0:435:da07:14cb with SMTP id b6-20020a056402278600b00435da0714cbmr6579060ede.408.1657304111299; Fri, 08 Jul 2022 11:15:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1657304111; cv=none; d=google.com; s=arc-20160816; b=TplZ25a4Jsecwh0Pts8SEn/APLQd7gLhrNlIop08Udj/wJoZ/kSTAqHu3DwU650cza mjTAomcf2XGuxYn/MCILtwEIlCJ7N2txp83sbSUVZsE0/wCNAsF6riuW1g6xTUKu8/1h nSaCDEP+acMDdTc0ykBrvF0P5CQ/lCeeM5EYcwd9RVk5GB3NAlr2rTiCpk5diPr+uiGJ 3gOFxEp6ybzmBahpmngfyvOswchXD87IB6MHBsR+pOxgPLQ9t7tPhHQ6F0apGyYgP+lX zCfcvAFsFEttZiOAHStKg/o7kvo1ZNFUaowGuRv7BIpvkBPVtaq4/9mGLyt8mB5gUMIG qLWw== 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 :message-id:date:subject:cc:to:from; bh=QZ+Fbq8BHItWdoD3i/VoO580Y4F1KXCfpFDhvT7QcwM=; b=wt3PiNP0SDRWVjgZhnkGXsiAqVwEIMGB1bT7vQZ+/iESEeXRiYKINoGEe3SpteL6FI QaRcluyGnYuvwTehi1D+H0A3iL9rrDdo56XL7qhKMiPCK7vmlk7MVL0rQ29AX1Rdu22c Fo9gZIFMD7l9i0C13het7/M6RLkYoEZXYKtiOlYy+LzaauB5t/Uz31JHQx4SRbhLWg4K XGTQjwDdIdz3HUTnDxWp3idUCYHGywVnV1QZMJRqMRkvGXMKTunU41D6k4Ngi5cKXZXi 93JTw4v5GXX7BuwXlDh4MVeiT6yUlSAtPJ6vgsOqFAO9XRqlFH80Y3FKwDjqlUBRft/d RP7Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ispras.ru Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id t12-20020a056402524c00b0043ab611258bsi1006639edd.627.2022.07.08.11.14.36; Fri, 08 Jul 2022 11:15:11 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ispras.ru Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238995AbiGHSAX (ORCPT + 99 others); Fri, 8 Jul 2022 14:00:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56162 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238493AbiGHSAV (ORCPT ); Fri, 8 Jul 2022 14:00:21 -0400 Received: from mail.ispras.ru (mail.ispras.ru [83.149.199.84]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F2FEB237C3; Fri, 8 Jul 2022 11:00:19 -0700 (PDT) Received: from localhost.localdomain (unknown [176.59.170.159]) by mail.ispras.ru (Postfix) with ESMTPSA id D068440D403E; Fri, 8 Jul 2022 18:00:08 +0000 (UTC) From: Fedor Pchelkin To: Robin van der Gracht , Oleksij Rempel Cc: Fedor Pchelkin , kernel@pengutronix.de, Oliver Hartkopp , Marc Kleine-Budde , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , linux-can@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, ldv-project@linuxtesting.org, Alexey Khoroshilov Subject: [PATCH] can: j1939: fix memory leak of skbs Date: Fri, 8 Jul 2022 20:59:49 +0300 Message-Id: <20220708175949.539064-1-pchelkin@ispras.ru> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Syzkaller reported memory leak of skbs introduced with the commit 2030043e616c ("can: j1939: fix Use-after-Free, hold skb ref while in use"). Link to Syzkaller info and repro: https://forge.ispras.ru/issues/11743 The suggested solution was tested on the new memory-leak Syzkaller repro and on the old use-after-free repro (that use-after-free bug was solved with aforementioned commit). Although there can probably be another situations when the numbers of skb_get() and skb_unref() calls don't match and I don't see it in right way. Moreover, skb_unref() call can be harmlessly removed from line 338 in j1939_session_skb_drop_old() (/net/can/j1939/transport.c). But then I assume this removal ruins the whole reference counts logic... Overall, there is definitely something not clear in skb reference counts management with skb_get() and skb_unref(). The solution we suggested fixes the leaks and use-after-free's induced by Syzkaller but perhaps the origin of the problem can be somewhere else. Found by Linux Verification Center (linuxtesting.org) with Syzkaller. Signed-off-by: Fedor Pchelkin Signed-off-by: Alexey Khoroshilov --- net/can/j1939/transport.c | 1 - 1 file changed, 1 deletion(-) diff --git a/net/can/j1939/transport.c b/net/can/j1939/transport.c index 307ee1174a6e..9600b339cbf8 100644 --- a/net/can/j1939/transport.c +++ b/net/can/j1939/transport.c @@ -356,7 +356,6 @@ void j1939_session_skb_queue(struct j1939_session *session, skcb->flags |= J1939_ECU_LOCAL_SRC; - skb_get(skb); skb_queue_tail(&session->skb_queue, skb); } -- 2.25.1