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 BA2864E66B0 for ; Wed, 16 Sep 2026 10:42:30 +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=1789555364; cv=none; b=BjP7JDaVt5LnKabL8kV8mP7Br1zYoz3SDF4VgsJXodRKt/Rk4sMYYeo8yzlKnYt9BxCeR54U9O9Py12GL29pnYJhlBxfi+k1vdBMqMMWHRXaZyqC/p91iWSKuf3Wi1yvQIob+8VjmN3S/OwJDFe3Qs8SeuNOJEnWZw+QnPfbUqw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789555364; c=relaxed/simple; bh=Z3XFLS7Pyc+ncgTjHrp3yaOYBGOryOfEyjjypyl8dKc=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=GrwGgUxil0NL0u9yo4yFo8tHMekuShgku4PWzHK4NCdG4OWhT6eXsmLjVaFSVabCbc4OykGAlC2TyNX9138tBb3dxk4mbcV3GEDuRSi2igskG1jMHve6sOn1wrYcBieiHzfZkKMT9Ahk06dNqKYp1gWJBCsYpel7jgXN2IWvt8I= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=tB0OeUuP; 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="tB0OeUuP" Received: by smtp.kernel.org (Postfix) with ESMTPSA id DAE681F000FF; Wed, 16 Sep 2026 10:42:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789555347; bh=v4rDws0xWy6uX566WdT6CbfZNhkETnO3PECCHMzGsF8=; h=From:To:Cc:Subject:Date:Reply-To; b=tB0OeUuPx+LwdjrOxdVc05zuRzWF71jauzbqyHEHbnUeCkGsMngDjtKZF9f2xiZSH CVSBhIiRaq5/l8oNPaHXfyJxNT1T6GMdhzT0Sp9Pv3SSRJqQbYb60eNuoIPpKV5MU7 NR3InzxCx2nHJ93NmABnROZ1TGan8gqIsVBchxyc= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-89988: kprobes: Protect kprobe_blacklist with RCU Date: Wed, 16 Sep 2026 11:31:58 +0100 Message-ID: <2026091657-CVE-2026-89988-e19b@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=3364; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=94o9RdH5DvCJ101ZpUjAI1L3ddmCM6yK1o9tPuK1n6A=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmr8pduSt66gbOKVYHNzoRDhlVAYNPK2+ZtJ4tPzFHIT 2Py1C3viGVhEGRikBVTZPmyjefo/opDil6Gtqdh5rAygQxh4OIUgIn4vmGYKyO7hbV8XldwiXPm Mr1/6yR+BNc4MMwPDz35pbWc8bp7hHZ7r5H2kvnr3WYDAA== 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: kprobes: Protect kprobe_blacklist with RCU __within_kprobe_blacklist() traverses kprobe_blacklist without holding kprobe_mutex. When a module is unloaded, kprobe_remove_area_blacklist() removes blacklist entries and immediately frees them with kfree(). A concurrent call to within_kprobe_blacklist() can therefore dereference freed memory. Furthermore, within_kprobe_blacklist() can be called in atomic or non-preemptible contexts where the sleeping kprobe_mutex cannot be taken. Protect kprobe_blacklist with RCU. Use guard(rcu)() and list_for_each_entry_rcu() for traversal, list_add_tail_rcu() for insertions, list_del_rcu() for deletions, and kfree_rcu() to reclaim entries safely after a grace period. The Linux kernel CVE team has assigned CVE-2026-89988 to this issue. Affected and fixed versions =========================== Issue introduced in 3.16 with commit 376e242429bf8539ef39a080ac113c8799840b13 and fixed in 6.1.188 with commit 8f406205003f741225f620f0e357ca0de71d45e3 Issue introduced in 3.16 with commit 376e242429bf8539ef39a080ac113c8799840b13 and fixed in 6.6.157 with commit 630ed8734a02b992e8a97538179c2ece42c5210f Issue introduced in 3.16 with commit 376e242429bf8539ef39a080ac113c8799840b13 and fixed in 6.12.110 with commit 518d9b5568bb06f86e4434f7a30faa9612ea91ad Issue introduced in 3.16 with commit 376e242429bf8539ef39a080ac113c8799840b13 and fixed in 6.18.51 with commit 5da247e4d1e8661d4d6f997101d59967e8994e32 Issue introduced in 3.16 with commit 376e242429bf8539ef39a080ac113c8799840b13 and fixed in 7.2.5 with commit 6e62cf983a2bd547e6bbd3f935539233e5f97f8f Issue introduced in 3.16 with commit 376e242429bf8539ef39a080ac113c8799840b13 and fixed in 7.3-rc2 with commit 0c4256196b3a105307e2235fbfd85e768bbcdd0f 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-89988 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: include/linux/kprobes.h kernel/kprobes.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/8f406205003f741225f620f0e357ca0de71d45e3 https://git.kernel.org/stable/c/630ed8734a02b992e8a97538179c2ece42c5210f https://git.kernel.org/stable/c/518d9b5568bb06f86e4434f7a30faa9612ea91ad https://git.kernel.org/stable/c/5da247e4d1e8661d4d6f997101d59967e8994e32 https://git.kernel.org/stable/c/6e62cf983a2bd547e6bbd3f935539233e5f97f8f https://git.kernel.org/stable/c/0c4256196b3a105307e2235fbfd85e768bbcdd0f