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 221325A9872 for ; Thu, 17 Sep 2026 16:34:45 +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=1789662886; cv=none; b=n0Nh4KQSvJ+BWnELmqtJogsEJlPPjpXLINPmEdky/0sSmp9hTnP2MGFw1PkPy8H2bLVjBJ/bapWUsS6ztjoJ0FmU9zwaXguohU74/3omoSz/FlUy7YSZfSe1+s63PLp4J0QQ/1ZJKl6D+KhV2E4MhNJzVCVzy2/ZAEsZ9rMnhIA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789662886; c=relaxed/simple; bh=9qe+6rVB6RH79DlRBPB1Rfagnt937N7OqybaAatsJu4=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=d4WkpmKCxPhvFFjt04gICwi1fCylXy3GuIFiTR0aezTe9mYE8paK2SFVWQVV8bIOmJfjQ6ghCVrDdivv1F3zI+PUQ3dBY85lcM4YgAJOIwoNyN0w+PPTkhVsACYfKDeQykuodsgF7KiYRnhsDf25NHZT9KsDlIXZH2LMGQuLWz4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=ifC7mG47; 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="ifC7mG47" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5DD821F000FF; Thu, 17 Sep 2026 16:34:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789662884; bh=/VMFFoGRKQMMEywleMJJAuAo1s6dBvcqkZfTG8S1zWc=; h=From:To:Cc:Subject:Date:Reply-To; b=ifC7mG47OyN7fEZxKtGE389P6/nW/tpXQfWhGeJpKZOwzQLWne66uHaUOGN+6T3Ji Bo8vWPH9TG9AA5bV17EisFRV7vjYzcIwv6gfCrgrBf0mRHWhwO8fNZGCxcjPi1Wz9d gu4PAdTISsii7iFTo6ORutGZLsPZEXxwVN7hlD2w= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-93054: uio: Fix stale info pointer in failed registration path Date: Thu, 17 Sep 2026 17:15:33 +0100 Message-ID: <2026091735-CVE-2026-93054-4e72@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=4079; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=VlqyALeJAhZZ+LrHLFLN5MbKS6SMNo9Nmr2CO04dDJg=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlrBPbPvbfqj0204dbeGVFMVza96JFbFPql9PnV23aBe wvrnR8FdsSyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBEMtcxzPcSrPnnXaciq2d9 vjvx9LR219rwbwzzK9KXqzkYKb7t1PPrO3hwwaGeZJWtAA== 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: uio: Fix stale info pointer in failed registration path After device_add(), the UIO device is visible to userspace and /dev/uioX can be opened. If a later setup step fails, __uio_register_device() unwinds the device but leaves idev->info pointing at the caller-owned struct uio_info. That is unsafe when an opener races with the failed registration path. The open file keeps a reference to the uio_device, while the caller sees registration failure and may free its struct uio_info. Later file operations can then follow idev->info and dereference freed memory. Handle post-device_add() failures like unregister: remove UIO attributes while the info pointer is still valid, then clear idev->info under info_lock and wake existing waiters/async users before removing the device and minor. This makes already-open file descriptors observe the same "device gone" state as normal uio_unregister_device(). The Linux kernel CVE team has assigned CVE-2026-93054 to this issue. Affected and fixed versions =========================== Issue introduced in 4.18 with commit a93e7b331568227500186a465fee3c2cb5dffd1f and fixed in 5.10.270 with commit 63eaa7663335d482a8825c231213e312cacea567 Issue introduced in 4.18 with commit a93e7b331568227500186a465fee3c2cb5dffd1f and fixed in 5.15.221 with commit df4faf65194ec6c315a59be4c6749eaeb3009243 Issue introduced in 4.18 with commit a93e7b331568227500186a465fee3c2cb5dffd1f and fixed in 6.1.188 with commit 506b43dde5f9ac0068b1360e6b5dbee07fda59fb Issue introduced in 4.18 with commit a93e7b331568227500186a465fee3c2cb5dffd1f and fixed in 6.6.157 with commit 15340b00e665af805523b08515294a1aa1778151 Issue introduced in 4.18 with commit a93e7b331568227500186a465fee3c2cb5dffd1f and fixed in 6.12.110 with commit 234156f6c6d9ec35dc47abbcc3adc3c79fc6a5ac Issue introduced in 4.18 with commit a93e7b331568227500186a465fee3c2cb5dffd1f and fixed in 6.18.52 with commit 16695e9059d80ea6661e8399064b0c01f641dd8c Issue introduced in 4.18 with commit a93e7b331568227500186a465fee3c2cb5dffd1f and fixed in 7.2.6 with commit ec5bd6731183eb6f619140c9bef2ee11ed818c20 Issue introduced in 4.18 with commit a93e7b331568227500186a465fee3c2cb5dffd1f and fixed in 7.3-rc1 with commit 67b6fc084b034a91c3ec7907a3fed89a2450f30b Issue introduced in 4.14.100 with commit 085d735c858934e5d5bfaedb1fc98bd9135e6ff1 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-93054 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/uio/uio.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/63eaa7663335d482a8825c231213e312cacea567 https://git.kernel.org/stable/c/df4faf65194ec6c315a59be4c6749eaeb3009243 https://git.kernel.org/stable/c/506b43dde5f9ac0068b1360e6b5dbee07fda59fb https://git.kernel.org/stable/c/15340b00e665af805523b08515294a1aa1778151 https://git.kernel.org/stable/c/234156f6c6d9ec35dc47abbcc3adc3c79fc6a5ac https://git.kernel.org/stable/c/16695e9059d80ea6661e8399064b0c01f641dd8c https://git.kernel.org/stable/c/ec5bd6731183eb6f619140c9bef2ee11ed818c20 https://git.kernel.org/stable/c/67b6fc084b034a91c3ec7907a3fed89a2450f30b