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 502405275A8 for ; Thu, 17 Sep 2026 16:34:33 +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=1789662874; cv=none; b=FqWi2wNxuJ4R7kjUkwVnkGYyUP2lLFwjcRqh+5HDglNJ6JdeSK2hMFGbzt6jbubO2JJGMxMpQK+wtLX8C13tqXurLpcn0KHWFbpBHtKz+in9YGMQUv1O/wiVJe3pPT5ZAUh2VECSvxjvJLhzUWPMjNy3O0tlhOUXiO9IqxWxwVI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789662874; c=relaxed/simple; bh=kaUOc2bgxErx9DvJq+qamI3GckAXHbA5Vp8mXSVHylw=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type; b=squ3BkeIZoDERAhSGVlGEl7hcEYPt10ncum7lvkEAfJ+iEFKEhjAVW2o9BU/9nuobuKfpNAJQr8smy0gmTxy4Ls14Xrgvqo8+Pb55LyjLZ8J4cFzX8jMEJhwLEIR4F80oO1mv05dSabaRcWevF0RK1F19qBRrJagtVVuY4fG3d4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=ly8LgwtF; 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="ly8LgwtF" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9F2031F000FF; Thu, 17 Sep 2026 16:34:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789662873; bh=SRQVe3xHgBb6kLlBwXK7eAq+4+OeUTnBhn0ARuAvnP8=; h=From:To:Cc:Subject:Date:Reply-To; b=ly8LgwtFdCLzRJEf+tjMXZnHev3gPhXWpMmrVFMgFzDZJEBrfeZsUHkoW9jMLUCAw YuzfKCQLUPkEYqtYyFPfHNgz7YNM1WhzwHxkJ6+t5dX3Eput+Ukee3PaHeAk6ALHD1 gsFAlzYXEQuYqvIt1XySDEuJatWAkfjHmaurh0N0= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-93050: ipack: ipoctal: fix UAF, null-ptr-deref, and use-after-free in cleanup on remove Date: Thu, 17 Sep 2026 17:15:29 +0100 Message-ID: <2026091734-CVE-2026-93050-514d@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=4015; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=NJRUo9ySGsAzj0az6lxNoCX/2HbVfU6rqJpgwWaS2zc=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlrBPat2lZ7/FiKwb0PX/4/uNBhtzyR5eR/edWclXc+t xQ+TGL63BHLwiDIxCArpsjyZRvP0f0VhxS9DG1Pw8xhZQIZwsDFKQAT4c1hmO+7ZPPlJbGfSn8t 5nyzf+7zK3xeRu8YFqxVVZn/68hshzCfUxEMCZHqpuL7ZwIA X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: ipack: ipoctal: fix UAF, null-ptr-deref, and use-after-free in cleanup on remove Three issues arise when the device is removed while a tty session is still active: 1. UAF of struct ipoctal: the remove callback frees ipoctal via kfree() while tty ops may still access it. Fix by introducing kref-based lifetime management — kref is taken in install() when a tty is opened and released in cleanup() when the tty is finally destroyed; remove() uses kref_put() instead of kfree(). 2. NULL dereference in ipoctal_write_tty(): __ipoctal_remove() frees xmit_buf via tty_port_free_xmit_buf() while a userspace process may still hold the tty fd and call write(). Fix by checking for NULL xmit_buf in ipoctal_write_tty(). 3. UAF in ipoctal_cleanup(): ipack_put_carrier(ipoctal->dev) dereferences ipoctal->dev after the ipack_device has been freed by ipack_device_del(). Fix by caching ipoctal->carrier_owner during probe() and calling module_put() on the cached pointer directly in cleanup(), avoiding any access to ipoctal->dev. Also introduce a "removed" flag in struct ipoctal, set at the start of __ipoctal_remove(), and checked in every tty op that accesses hardware resources (port_activate, write_tty, set_termios, hangup, shutdown). This prevents page faults when devm_ioremap() regions are unmapped after remove() returns. The Linux kernel CVE team has assigned CVE-2026-93050 to this issue. Affected and fixed versions =========================== Issue introduced in 3.8 with commit 05e5027efc9c0bb6d1d04cde279afbafca0a7929 and fixed in 6.1.188 with commit ab5f5b27a340004b92252c6a5f23bf1c6cf3b02a Issue introduced in 3.8 with commit 05e5027efc9c0bb6d1d04cde279afbafca0a7929 and fixed in 6.6.157 with commit c92ef8fd834521f0b788e0511976c689fe57c63c Issue introduced in 3.8 with commit 05e5027efc9c0bb6d1d04cde279afbafca0a7929 and fixed in 6.12.110 with commit a4613140f01bd0fb9980e2746ed9aaa65a29b5d6 Issue introduced in 3.8 with commit 05e5027efc9c0bb6d1d04cde279afbafca0a7929 and fixed in 6.18.52 with commit 1a3258e105f711538201bdd2ac2a05b11554eabc Issue introduced in 3.8 with commit 05e5027efc9c0bb6d1d04cde279afbafca0a7929 and fixed in 7.2.6 with commit 4a6518be316029650301f2a5e8f0def229b895d9 Issue introduced in 3.8 with commit 05e5027efc9c0bb6d1d04cde279afbafca0a7929 and fixed in 7.3-rc1 with commit b6b5d64cb161a28347d64dc3168a636c4abb68d5 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-93050 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/ipack/devices/ipoctal.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/ab5f5b27a340004b92252c6a5f23bf1c6cf3b02a https://git.kernel.org/stable/c/c92ef8fd834521f0b788e0511976c689fe57c63c https://git.kernel.org/stable/c/a4613140f01bd0fb9980e2746ed9aaa65a29b5d6 https://git.kernel.org/stable/c/1a3258e105f711538201bdd2ac2a05b11554eabc https://git.kernel.org/stable/c/4a6518be316029650301f2a5e8f0def229b895d9 https://git.kernel.org/stable/c/b6b5d64cb161a28347d64dc3168a636c4abb68d5