From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795154600; b=NBxz1LK2+GYGPXyuXPeKYyS16941LaqFlY+1sIIL9HZ9XdMFybbyd5iZgoYDEVeJ03wv UfmbNrkUiqH3Co4ncDK82znCCxFOwjut8GMEpAQOjXv1iWV2LeYvg20vx5osCl7dQk8BB OXB4RqH22IUAup3N5LjFZ2vW0c5JCSutDpEljjjT87lYW8iNm3s6I8YCThQAeuyF+EkYz SxBTpdutFnZ+Agich5qaJrQZ3ZQvQniK4CNlY/pyvT9qGS7UlT8RzQlm50dGS5t8qya98 /6eF9H5mw+fQVSnV7PUE/D8V6Get0YJsZVBcuaj/5RUVXCo9uqrygb1U3nQoyM8pg1Q== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154600; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=UNSIWLSLfMynDRqyiHVobQ9+xZhWczT/6NEeo9Abxq8=; b=jFrmo/4sknOKNi58ZLgLEGUldhU0eJBm43huFUL8jO3nOOFU0rkjSMkCTKA5mQgBo/PP HoLFwYvu9VsfAx5YZHk8OLhZr4qFRwioH1U5bXXyfUI2qDFR+cWBKTJwzP6C9nZdLUAzS U5iyLxMP/WR0qhJBall6jlaQrxaDeW+wx1+wgf512PIMdG/PNdwlheUQOKEv6K6D93tTz W9xi6EZ8qUXsNLWkuUOFcUwg6FDgvwbRhW59W7utrYQe/ZZmWUT4mExikM+HQIMGtFYxL OGskqoktwa0nG/pptn4qmudmmSCWZ8TxyPwYtxyY/dZ7od0CKyM4hWEOdckDEt5a7GQ== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=n8B8fC4g; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A21C1606A51B for ; Fri, 20 Nov 2026 06:03:20 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=n8B8fC4g Received: by smtp.kernel.org (Postfix) with ESMTPSA id F0C5B1F000D0; Fri, 20 Nov 2026 06:03:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154600; bh=UNSIWLSLfMynDRqyiHVobQ9+xZhWczT/6NEeo9Abxq8=; h=From:To:Cc:Subject:Date:Reply-To; b=n8B8fC4gm557Qgm86E+8xAAG646K9prdXjhDtiP4v6d4cxhhra/v0FTeJI62NQo08 X7oVx1Ku+6FfdN1/NFzMQnMFBlew0m+yAMvxpngzjGJCD6/w/JkReR1PEpHV8bn1DG seRxOlXyAWPYLaq+jE4B/O2VUni+oSmUbwCQF5bw= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99763: 9p: don't decrement a server-owned zero nlink Date: Fri, 20 Nov 2026 06:52:29 +0100 Message-ID: <2026112025-CVE-2026-99763-e15f@gregkh> X-Mailer: git-send-email 2.56.1 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=4021; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=/VEvXlZ66f4xNRIrh8JCJtQy1S2TqbciJHCYT+ln+MM=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/7y9M+XFDhGFX6KXdU7Yu4d0/I/PGdD3e3UsfTJrV0 FR+SYAxtSOWhUGQiUFWTJHlyzaeo/srDil6GdqehpnDygQyhIGLUwAmsvU9w4JZVyqe9j1ZYNlx 4oTz9J7IGcuen5jOsGBz4QzdP1Ou/f8vYXakabLxh5wf198CAA== 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: 9p: don't decrement a server-owned zero nlink A 9P2000.L server can report nlink=0 for a regular file that still exists. On a cache=loose or cache=fscache mount, lookup stores that value with set_nlink(). A later successful unlink calls v9fs_dec_count(), which still calls drop_nlink() for a non-directory. drop_nlink() warns, and the unsigned link count wraps to 4294967295. fstat() on a descriptor opened before the unlink shows 0 before and 4294967295 after. The warning on the unpatched kernel, trimmed: WARNING: fs/inode.c:408 at drop_nlink+0xac/0xd0, CPU#1: trigger/188 CPU: 1 UID: 0 PID: 188 Comm: trigger Tainted: G N 7.3.0-rc4-00537-ga3ff15db6820 #1 PREEMPT(lazy) RIP: 0010:drop_nlink+0xac/0xd0 Call Trace: v9fs_remove+0x529/0x750 vfs_unlink+0x2f0/0xbd0 filename_unlinkat+0x340/0x6c0 __x64_sys_unlink+0x46/0x70 do_syscall_64+0xe8/0x4f0 entry_SYSCALL_64_after_hwframe+0x77/0x7f ---[ end trace 0000000000000000 ]--- Directories whose cached nlink is at most 2 already skip this decrement, because the exported filesystem may not maintain nlink (commit ac89b2ef9b559). cache=none skips it as well (commit 574aa0b479947). cache=mmap does not take this path: it sets neither CACHE_META nor CACHE_LOOSE. A regular file on cache=loose or cache=fscache still does. Its count came from GETATTR and may already be zero, so skip the decrement when i_nlink is already 0. Verified on 7.3-rc4-00537-ga3ff15db6820 with only this change. A server that advertises nlink=0 and accepts the unlink no longer warns, and the open descriptor stays at nlink 0. An honest server on the same mount still goes from 1 to 0. A rejected unlink leaves the count unchanged. cache=none is unchanged. With panic_on_warn the unpatched kernel panics on the warning; the patched kernel does not. The Linux kernel CVE team has assigned CVE-2026-99763 to this issue. Affected and fixed versions =========================== Issue introduced in 4.17 with commit ac89b2ef9b55924bcf922251f043ba73a32d05bb and fixed in 6.12.118 with commit 5980952fa41f822440f90df7e4628d4b61d22589 Issue introduced in 4.17 with commit ac89b2ef9b55924bcf922251f043ba73a32d05bb and fixed in 6.18.64 with commit 9ea87af4e675ae5c3781f2f362c062a13a93fe15 Issue introduced in 4.17 with commit ac89b2ef9b55924bcf922251f043ba73a32d05bb and fixed in 7.3.5 with commit 8d247ae04b11459bc7d2ee295c2327e16a0e2893 Issue introduced in 4.17 with commit ac89b2ef9b55924bcf922251f043ba73a32d05bb and fixed in 7.4-rc2 with commit 4e915aa8566173b44146bc46177c85afbe6bdf96 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-99763 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: fs/9p/vfs_inode.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/5980952fa41f822440f90df7e4628d4b61d22589 https://git.kernel.org/stable/c/9ea87af4e675ae5c3781f2f362c062a13a93fe15 https://git.kernel.org/stable/c/8d247ae04b11459bc7d2ee295c2327e16a0e2893 https://git.kernel.org/stable/c/4e915aa8566173b44146bc46177c85afbe6bdf96