From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from submarine.notk.org (62-210-214-84.rev.poneytelecom.eu [62.210.214.84]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 22A2612C49A for ; Fri, 10 May 2024 14:23:52 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=62.210.214.84 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1715351036; cv=none; b=L4HrGNbAkN8zfSZmT/Dt+dvM0J5K2mlRq9qoi7Yktuabs4DaOTzkDrJCDFwfrypnG5dJR0jzzMfTwY6oaJE+nkgZRgwN+liGdS6QPw9rWzw+jEsVfeVQDSTvhEdFtwhrYrGLpnokvqQSbSk5UJHIaJDU9wfwn/nz6uPpPzUdkbQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1715351036; c=relaxed/simple; bh=i5TyrrTHj5tpvHv/9wICnh9yDMkt6Jws8WcmLr/O/44=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Q+W3D8iCSX15WvTPQ/FWPpZO4K8K7S/YFq3/hSSk67dslqULwIi0aZbPC8fMElMLGaHPVMkYeBT7p5uX/J/bEN8+Hi3iyuiiZamwKtJIX3KipIoI9/YeZEGKFAUEWilPPFW2ISoPt/QTQYKgWXXFa8cs8SZbxaFJfO100fduCzY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=codewreck.org; spf=pass smtp.mailfrom=codewreck.org; dkim=pass (2048-bit key) header.d=codewreck.org header.i=@codewreck.org header.b=VAm2divA; arc=none smtp.client-ip=62.210.214.84 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=codewreck.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=codewreck.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=codewreck.org header.i=@codewreck.org header.b="VAm2divA" Received: from gaia.codewreck.org (localhost [127.0.0.1]) by submarine.notk.org (Postfix) with ESMTPS id 627B414C2DB; Fri, 10 May 2024 16:23:50 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=codewreck.org; s=2; t=1715351031; h=from:from:reply-to:subject:subject: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=y0Rwysq4bAvF6adPo4fCiuwoVubXcZKN7gxYVT6zVK4=; b=VAm2divABxt2aDDQge/jvw0E27ewg9h6JpupieolrBpI1US8gblBFF2w9KR/n9VGUqW0VT 9s6QiueFmmNRiH91wUGVB9j8/ThDbT7VvGSwqDbOJArWhbNqMlHYAGrdRGs8pNa5FY3apr P7S6MIzsa9ZNJUjsA0EO6BKlndZW6SXlTqou18dCjz+D5RE18OhIafLA25uq5MJ/rI6EOc Zi9WUcHNiWz677hAdXd1QyWk5cX46TfasQzfLPHeYLGG86zCPlIlw4dx4xqUjXAN/5nNeW ITCHZWxnkfOJ9/P5iu4RUGiDAqFtfrjqpBTArGo6QcN4wMA26V1Lwhx0fZot7g== Received: from localhost (gaia.codewreck.org [local]) by gaia.codewreck.org (OpenSMTPD) with ESMTPA id e7f7255e; Fri, 10 May 2024 14:23:45 +0000 (UTC) Date: Fri, 10 May 2024 23:23:30 +0900 From: Dominique Martinet To: Greg Kroah-Hartman Cc: cve@kernel.org, linux-kernel@vger.kernel.org Subject: Re: CVE-2022-48655: firmware: arm_scmi: Harden accesses to the reset domains Message-ID: References: <2024042859-CVE-2022-48655-5feb@gregkh> <2024051041-resisting-chatroom-32c8@gregkh> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <2024051041-resisting-chatroom-32c8@gregkh> Greg Kroah-Hartman wrote on Fri, May 10, 2024 at 09:55:15AM +0100: > > I can submit an edit as a patch to vulns.git json, but this doesn't seem > > overly important so for now a mail will probably do. > > the json and mbox files are generated by tools, so patches to them is > not a good idea as they will be overwritten the next time the scripts > are run. Just let me know what's the most convenient; if mail it is I won't bother :) > > >From a quick look it would seem it fixes arm_scmi from the addition of > > scmi_domain_reset() in 95a15d80aa0d ("firmware: arm_scmi: Add RESET > > protocol in SCMI v2.0"), which first appeared in v5.4-rc1, and does not > > appear to have been backported to older kernels, so v5.4+ can be added > > as a requirement. > > We can add a "this is where the problem showed up" if you know it, so > that would be 95a15d80aa0d ("firmware: arm_scmi: Add RESET protocol in > SCMI v2.0"), correct? Yes; this commit adds the out of bound access. > > This means the current 5.4/5.10 trees are affected; the commit doesn't > > backport cleanly because of a trivial context conflict so if that helps > > I can send a couple of stable patch if that helps even if our systems > > are not using arm_scmi (CVEs also don't have any way of expressing > > whether the affected driver is used (or even built) at all, so I guess > > people with affected versions will have to check that themselves...) > > As everyone has different configurations, yes, everyone needs to check > themselves, there is no way for us to determine this at all. But we do > list the files affected, so that should help you out in determining this > automatically on your end. I didn't see hte list of files anywhere for this, does it depend on the commit? (not that it's a problem to look at the commits referenced, I don't think we'll automate anything for the forseeable future) > And yes, backported patches would be always appreciated for older > kernels if you have them. Sure, I'll take a min to finish the patches and send them on Monday; might as well use work time when I've got an excuse to do kernel stuff. Thanks, -- Dominique Martinet | Asmadeus