Received: by 2002:a05:6358:53a8:b0:117:f937:c515 with SMTP id z40csp5037615rwe; Tue, 18 Apr 2023 00:48:49 -0700 (PDT) X-Google-Smtp-Source: AKy350YI7D95H2xzDasUM2GGskneTdJJHmsSX92uaxzU3meT+xRIiCuM47oDGLYGsX69+AFAAZ4O X-Received: by 2002:a05:6a20:7f81:b0:f0:5e28:b9f5 with SMTP id d1-20020a056a207f8100b000f05e28b9f5mr3729942pzj.3.1681804108940; Tue, 18 Apr 2023 00:48:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1681804108; cv=none; d=google.com; s=arc-20160816; b=NJMZ1hgjKHbQA2avyZnwhwOjAGTHlWtS5iWBQiBbZjGdQ25ewsmyIYXLM58+1nnJkp cxW4142OqBR9IZpAKThOBUusngvH6pZDaFcs1mjvMrDLFruJUT47cV3ATX3w5Fgf7I47 fDptSqb2N60xDDQ88KhGYyAlW2q6oHevoHuZqg35p34p76JXwW0Vfj96atSKuSooVbH5 RhjD7sOEIcMPkyygUTYlJdm/W5szedR+nbpOHPVPnY+AyG5vNoyVlexxMsT+2VKTwAOb UgXpWsrD3UYgaUt2hvOMK5IqjN2kiWxJ/eBo1u4YITeEQUYZ/4VPU4GgGpdoPJM3otoj lIFQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:in-reply-to :subject:cc:to:from:message-id:date:dkim-signature:dkim-signature; bh=eMC66crlZNa13iNMbBSheE0yhYEzTw0dIUu1wy+r0sc=; b=Sh4TjO74oOiYydbUoIw0lPmql06NZ0xKpUCDvrRsW4s8u8Xp3aFOl0kRYPUe58Ruxt XMFOtzZNcouVJg+Fly0oQgaC9JIes7vSIf5xGthdcZAM8NLvjCxuuHTwh8HXuYJs7ftv zjNt+c4Hs5V4+NUzOu/JpEwTmFVbLvLmnDG0vusEBPSTm4VMT5XeXoTE5lJ5MFc3VOyA vuFPoarNG9/Dc/CTPohJ4cKLEAEZ2024YSyqOanW24E3Zb3/Pq31/5ViJCr2+xz7eP14 gYwBCRG9yQQyqrDoDja8he3//xVC1hEiATUrz85GT8zfnV4LhAuoXd/x67MFNR16f5IN Z7yQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=UyFUJMBq; dkim=neutral (no key) header.i=@suse.de; 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=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id j123-20020a625581000000b0063b54fd1f02si12199924pfb.196.2023.04.18.00.48.17; Tue, 18 Apr 2023 00:48:28 -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; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=UyFUJMBq; dkim=neutral (no key) header.i=@suse.de; 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=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231233AbjDRHre (ORCPT + 99 others); Tue, 18 Apr 2023 03:47:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54980 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230244AbjDRHr2 (ORCPT ); Tue, 18 Apr 2023 03:47:28 -0400 Received: from smtp-out1.suse.de (smtp-out1.suse.de [IPv6:2001:67c:2178:6::1c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CDE2E7DB3; Tue, 18 Apr 2023 00:47:04 -0700 (PDT) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 6A42221A15; Tue, 18 Apr 2023 07:47:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1681804023; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=eMC66crlZNa13iNMbBSheE0yhYEzTw0dIUu1wy+r0sc=; b=UyFUJMBqBgacdQ/J1yd44TsnZ9DNQwBuF5Pi17LBhF/i/GinFUz7svvOiO/J9tNxNBeC+A XI5YF/TytBzgDeQvtQiwam/OEndilDqzi6pcrB4H1HFTy/3W9tRdqQrjf9BGDtOsBzd0b3 m7aNUQxIB+zWhY5gu2/C0hLBocu6PTc= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1681804023; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=eMC66crlZNa13iNMbBSheE0yhYEzTw0dIUu1wy+r0sc=; b=hU4Djo3l//yID6wYySd0HqVlLgS9i78pMRPdZw3eTw1rL9sHmDrSKg8W6xIiIxJFp0QJII wtSBWrECgKg+nlBw== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 4E7C4139CC; Tue, 18 Apr 2023 07:47:03 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id VXpiEvdKPmQZbAAAMHmgww (envelope-from ); Tue, 18 Apr 2023 07:47:03 +0000 Date: Tue, 18 Apr 2023 09:47:02 +0200 Message-ID: <87ttxd4op5.wl-tiwai@suse.de> From: Takashi Iwai To: Andy Gross , Bjorn Andersson Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: Missing qcom/mdt_loader.c fix for CVE-2022-40540? In-Reply-To: <87ileq5ktl.wl-tiwai@suse.de> References: <87ileq5ktl.wl-tiwai@suse.de> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.2 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED 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 On Fri, 24 Mar 2023 14:40:38 +0100, Takashi Iwai wrote: > > Hi, > > I was asked about the handling for CVE-2022-40540 [*] on SUSE kernels, > and through a quick glance, the upstream code still misses the fix. > Namely, the downstream fix for the integer overflow check of the > firmware size below: > https://git.codelinaro.org/clo/la/kernel/msm-5.10/-/commit/dae3214cd3495e5c4b37537cacf665d2cdeaea24 > ... can be applied to the current upstream code (as of 6.3-rc3) as far > as I understand. > > Could you guys check it and apply the fix if really needed? Any news on this? This security issue seems still present in the latest upstream and linux-next. thanks, Takashi > > > Thanks! > > Takashi > > [*] > http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40540 > https://bugzilla.redhat.com/show_bug.cgi?id=2180513 > https://www.cve.org/CVERecord?id=CVE-2022-40540 > https://www.qualcomm.com/company/product-security/bulletins/march-2023-bulletin