From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5EA884DEC3F for ; Thu, 17 Sep 2026 16:37:00 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789663021; cv=none; b=HwIcb5PWAuRBi6PDYnhahrHrx2mP8bSiZ3oxCoXNYOxgElewzcMCXXpVXRvoDNDunlic1GBaeYjQb73Kk7wCXUTrCiiTITUyHV2BHiuOFJMs1x6SVc8laihx2VPH/2pFXKuFgKt2HMlvD00cWkHI6aKfspH5FOBl8F328vgVD7g= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789663021; c=relaxed/simple; bh=FJkJLb1MfQGNS4jVuYd//gLe2nI8EAjoVH5+V4GkVfE=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=lDFBVovtn3XnnYhwYfso3DbYFh3+ZG8LhS5AwwNidhNyJIZJA4PDxfZAA57jW7K4pw1vb2LkXfEiFZ9/Zhl4jnfEMlS5jdgsFgbUHOsM97XLSMnVOO8dnLn90dx9PHEUWfgJgsv9pqq1OwDKmp/fVeyooUfn40po0eRSN8KK5KM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=hvvxbwJN; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="hvvxbwJN" Received: by smtp.kernel.org (Postfix) with ESMTPSA id B30B61F00893; Thu, 17 Sep 2026 16:36:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789663020; bh=G58SULI8DWymBvf0aXwahC1qg+DZbGqhXLHlmTdnO+8=; h=From:To:Cc:Subject:Date:Reply-To; b=hvvxbwJNTkBfNUELb2fn0mA9t8oLkUNmjzpB0FMm7x8KCtc6mNUZnetSMSok4FXaP CBHSmpWMUiYnFZEJHiYS+7c4R+IfPtl+jc9NFX9VOxcXBexpjDBaQxR+WqTPT8B1NP nsB4Omrz3h/S2p2uGFsyBJE6QtNL6/P/zZMOZRC8= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-93072: irqchip/renesas-irqc: Fix generic interrupt chip leak on remove Date: Thu, 17 Sep 2026 17:15:51 +0100 Message-ID: <2026091739-CVE-2026-93072-e753@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3329; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=6DkvOc3WiHtdfFlp+YeEzSyacPtltmB5QzbTbmZnpyE=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlrBA7vPCQiIb6mg//o8Zg3X+oCjz65U/56QfROt6I/K 5eceOB2tyOWhUGQiUFWTJHlyzaeo/srDil6GdqehpnDygQyhIGLUwAm8u8jw1yRKQef+sYk7ZrH 0vncRfzsxF9T8xwZ5lkz6O97Iv3gfIV4+XaD4q6Sfy5fdwIA X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: irqchip/renesas-irqc: Fix generic interrupt chip leak on remove The driver allocates domain generic chips probe. However, on driver removal, the generic chips are not automatically freed when the interrupt domain is removed because the domain flags do not include IRQ_DOMAIN_FLAG_DESTROY_GC. This causes both the domain generic chips structure and the associated generic chips to be leaked. Additionally, the generic chips remain on the global list and may later be accessed by generic interrupt chip suspend, resume, or shutdown callbacks after the driver has been removed, potentially resulting in a use-after-free and kernel crash. Fix the resource leak by setting IRQ_DOMAIN_FLAG_DESTROY_GC on the interrupt domain; this lets the interrupt domain core automatically release all generic chips when irq_domain_remove() is invoked, removing the need for manual cleanup calls in error paths and remove callback. The Linux kernel CVE team has assigned CVE-2026-93072 to this issue. Affected and fixed versions =========================== Issue introduced in 4.4 with commit 99c221df33fbfa1b30e15dee879eb0a9ae1be353 and fixed in 6.6.157 with commit 3d39757ef791f90028da9c8b7c1fbbb497237e58 Issue introduced in 4.4 with commit 99c221df33fbfa1b30e15dee879eb0a9ae1be353 and fixed in 6.12.110 with commit 4bf7614d048434326081eef0ebef33cb77fe2ffc Issue introduced in 4.4 with commit 99c221df33fbfa1b30e15dee879eb0a9ae1be353 and fixed in 6.18.52 with commit 9acc996cb2e8477ae81bd7c067fec15202d6bc89 Issue introduced in 4.4 with commit 99c221df33fbfa1b30e15dee879eb0a9ae1be353 and fixed in 7.2.6 with commit 7c614f83301d464e2fb498d63552490d137ea10d Issue introduced in 4.4 with commit 99c221df33fbfa1b30e15dee879eb0a9ae1be353 and fixed in 7.3-rc1 with commit 616dd89d81ad9a3cf1cfff4088a4c43e4e00d6ba Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-93072 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/irqchip/irq-renesas-irqc.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/3d39757ef791f90028da9c8b7c1fbbb497237e58 https://git.kernel.org/stable/c/4bf7614d048434326081eef0ebef33cb77fe2ffc https://git.kernel.org/stable/c/9acc996cb2e8477ae81bd7c067fec15202d6bc89 https://git.kernel.org/stable/c/7c614f83301d464e2fb498d63552490d137ea10d https://git.kernel.org/stable/c/616dd89d81ad9a3cf1cfff4088a4c43e4e00d6ba