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 7C3E934B1A5 for ; Sun, 18 Oct 2026 15:46:39 +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=1792338400; cv=none; b=oU09+LJLLoPvtkEVXL1agoCc8n3chI/uB5rMmFL4hpJLTmKggiY+xPVSmtqZcIj7U8Ij+8XH5p+hkzMG5rtEVZtO7Puem8YANfGfwbGDCyl5tmjdXFg63Uvl6Ygh8GIdQw/pi+R2j/A67+DKZ31kHvq1Q1WImYYQasaf3MqwkiA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1792338400; c=relaxed/simple; bh=cAEcldOjGIze3H2NFTQ9KtGXhsBmmwCujpcIHxQl118=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=j/HwgVKRQ827usOlYQO0ZbJRPdt6T5C/ihvJwKdbchN+fwho2HjKgudlrMt1YTM/ZBDKvheu+XrkIXJCDcu7P2E5bWlHKgHOghGzhwQK/ktcy1+yIlsennFjvSshZ+yMVZ7eHxZxYU7dyYqX8NfmfyIXBWXJaIL4z2Uv6lMB3iE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=ftatcV6T; 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="ftatcV6T" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 089981F000C4; Sun, 18 Oct 2026 15:46:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1792338399; bh=/0IT7ATA7jwNLhHASf9mzJkpJeesIRq1r+k44vgwwi0=; h=From:To:Cc:Subject:Date:Reply-To; b=ftatcV6Tw0Sja4ddBOuFDRnRh93tt3nGlX0VuUO33zyLcHwSncQfLhZ/eb88LhEko yJ8JrfjTnGh6AlhqB6YUnfABa5c8l+tnTcoyveb6BNQHjUfyA6vXQ4B2Sz5UZQXm54 bXia9LsBR2KwW4ga+vaXtr79QDZh80jlgnVHMaKs= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-98669: iio: buffer: serialize buffer teardown with mode claims Date: Sun, 18 Oct 2026 17:44:04 +0200 Message-ID: <2026101858-CVE-2026-98669-4ec5@gregkh> X-Mailer: git-send-email 2.56.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=2962; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=dxgs9M9tbCXDNcYUeuIf8wp4K2WaZwctCfZWsIa8LxI=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlXXtpF3bx9OHVWWujRkD/N34Nk4w84XzijueCjWPgK5 9otCqwXOmJZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAitowM8xQqdfLu9W9xs9/i djPeimvupX4JdYYFm14x66lkXLr25b1b0t3P+em3EyIsAQ== 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: iio: buffer: serialize buffer teardown with mode claims Buffer-mode claims hold mlock to guarantee that the device remains in buffer mode until the claim is released. Normal buffer updates take info_exist_lock followed by mlock in iio_update_buffers(). However, iio_device_unregister() disables and deactivates all buffers without taking mlock. This can invalidate buffer state, including active_scan_mask, while a buffer-mode claim is held. Take mlock in iio_disable_all_buffers() so that unregister honors the mode-claim lifetime guarantee. The info_exist_lock -> mlock ordering matches iio_update_buffers(). The Linux kernel CVE team has assigned CVE-2026-98669 to this issue. Affected and fixed versions =========================== Issue introduced in 6.2 with commit 0a8565425afd8ba0e1a0ea73e21da119ee6dacea and fixed in 6.12.113 with commit 89f3852a28fcf7bab599280cb082baa0675536db Issue introduced in 6.2 with commit 0a8565425afd8ba0e1a0ea73e21da119ee6dacea and fixed in 6.18.56 with commit b466db9e68b4741af85f6c017e2bb0a2f025053f Issue introduced in 6.2 with commit 0a8565425afd8ba0e1a0ea73e21da119ee6dacea and fixed in 7.2.10 with commit e63188d77e10c0951bf67da6c295f768fd1abf4b Issue introduced in 6.2 with commit 0a8565425afd8ba0e1a0ea73e21da119ee6dacea and fixed in 7.3-rc6 with commit 84bb0fc46ccf6a545b8fdf57cda83770186ed8dd Issue introduced in 5.15.137 with commit a9c471892d75847671a246619c2148578f22bbc6 Issue introduced in 6.1.60 with commit 7bca0af538a49dacb1470f233be0676bdc09605b 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-98669 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/iio/industrialio-buffer.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/89f3852a28fcf7bab599280cb082baa0675536db https://git.kernel.org/stable/c/b466db9e68b4741af85f6c017e2bb0a2f025053f https://git.kernel.org/stable/c/e63188d77e10c0951bf67da6c295f768fd1abf4b https://git.kernel.org/stable/c/84bb0fc46ccf6a545b8fdf57cda83770186ed8dd