Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 6CACDCA6C92 for ; Tue, 27 Jan 2026 08:45:53 +0000 (UTC) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1vkehS-00063N-Mj; Tue, 27 Jan 2026 03:45:27 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1vkehQ-00061S-5Y for qemu-arm@nongnu.org; Tue, 27 Jan 2026 03:45:24 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1vkehJ-00038B-Bu for qemu-arm@nongnu.org; Tue, 27 Jan 2026 03:45:23 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1769503507; h=from:from:reply-to: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=8nZVq5C60OyjBjIgX/8zGTHHq0obTGLsoT+49US/5aA=; b=RAf/rSgIlITYL0KeWnUUcCLz6GOcnSPnTR+8ZYo0ruOOZQ7NcfjYpH3QgITnRscXBIhQEC 2lM3CoV38TCSfjv3Z4EYl/ELz51UFOkNCK8GpOTr/w00/x4raE50lf+/gQx+ZJT9kGPRlt aFiv/gcZOVD5mYX19nWT4WYsA4WEygY= Received: from mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-180-hD5EHANROQ-qoBP_gNrMJg-1; Tue, 27 Jan 2026 03:45:02 -0500 X-MC-Unique: hD5EHANROQ-qoBP_gNrMJg-1 X-Mimecast-MFC-AGG-ID: hD5EHANROQ-qoBP_gNrMJg_1769503501 Received: from mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.93]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id C5EEC18911AA; Tue, 27 Jan 2026 08:44:53 +0000 (UTC) Received: from redhat.com (unknown [10.45.225.228]) by mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 024F0180009E; Tue, 27 Jan 2026 08:44:47 +0000 (UTC) Date: Tue, 27 Jan 2026 08:44:43 +0000 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: Elhrj Saad Cc: =?utf-8?Q?C=C3=A9dric?= Le Goater , Peter Maydell , qemu-devel@nongnu.org, qemu-arm@nongnu.org, Steven Lee , Troy Lee , Jamin Lin , Andrew Jeffery , Joel Stanley , Michael Tokarev Subject: Re: [PATCH] hw/adc: Fix out-of-bounds write in Aspeed ADC model Message-ID: References: <20260126141820.719492-1-clg@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.2.14 (2025-02-20) X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.93 Received-SPF: pass client-ip=170.10.133.124; envelope-from=berrange@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-arm@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Errors-To: qemu-arm-bounces+qemu-arm=archiver.kernel.org@nongnu.org Sender: qemu-arm-bounces+qemu-arm=archiver.kernel.org@nongnu.org On Mon, Jan 26, 2026 at 07:22:23PM +0100, Elhrj Saad wrote: > Hello, gentlemen, > > Is there any possibility of making an exception and assigning a CVE for the > issue ?? (It's my first ever found vulnerability :) Thank you for your contribution to improving the quality of QEMU. In many projects this would indeed qualify for assignment of a CVE, but as Peter mentions, this falls outside the scope of QEMU's security policy. Assigning CVEs has quite a ripple effect on those consuming QEMU, due to it triggering many security response processes. As such we do not wish to issue CVEs for things that the project considers to merely be hardening bug fixes in an area of code that is not designed to be providing a security boundary. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|