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=1795154457; b=RjkvaETxMrbW9RLOuAFwGqVrlTn49ztteosSRhH5Po+WTYnQJi/7P4LWXQTbES6wUxQ+ iBtS5bTBekhWesqLBpPAe2mZLuZl5McE3fb1nTQY9yKUlcj5eg9CwLsqYjJyneEuarIFF KxnS/Cq23HqbdtCVtetNercEvbp10/vw4Aixuq4sDOEZb/QCwFifpSTX9qN3cFxXA94v8 DjQqLgWyZqa7pBjnPmtyiCh208I4NCnx5lZOKlM4lcCTfsoBh3OKBMJQQwN7lArcY2LVM mjMFA33UJFim3JJ+Cbn+slTWSESwfxHhrarGTpp8u+xervE8lU3B6DLAfNUDBoXcwzQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154457; 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=0bE3FgyPuhxHvos0VtzzyzeGzApMNSjXgWT3vclJ/H8=; b=bnRmhUU9MESRXGnEV0ReKbAT1/Yws3nKVFpxuCPJo4n6capmtbj++Gggh8mRzlvo1gj7 dQg2xsAR5qNLXlvEWQilqnl7KVKONQKSKU5pbIJHd83cqjfGaPZ1tUUB4y0YpVTPboVKx w01sElokSvQJ4RUTdINoWZH1bf09YK3t1LtDUnJrKuhsxFcmuoTvq3YosnrJE65Myz618 4ot4kJiBFsoSdepqj2QCfFhfGPqh+XOKhLtpWZhVuEjc20DONg134QHm9ENFlThZhX64F xIcKyhqARv1KrtxuT7+tOPgXVOfR92h9vaXxCct6Ylu1lfcjbuMXsnpHnYhbPmzVrIg== 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=MYvej7vf; 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 82A28606A510 for ; Fri, 20 Nov 2026 06:00:57 +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=MYvej7vf Received: by smtp.kernel.org (Postfix) with ESMTPSA id D3B3A1F000CF; Fri, 20 Nov 2026 06:00:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154457; bh=0bE3FgyPuhxHvos0VtzzyzeGzApMNSjXgWT3vclJ/H8=; h=From:To:Cc:Subject:Date:Reply-To; b=MYvej7vfGnMxuuWRBcf4M9Q5mqU8c7CZ06Yda15fRqzF2WwOVPGNm7Zf/Ofi6ooIm y8vf2QyNI4hbYmiuaKL2SzIHYbcMMl3d/DH6Fx+dcNzin/QYQHbRJHYRCqHLHpGzST WL+NfVH6l24B/uczNAzNA39IsLnPcnK18V2PPal8= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99749: ksmbd: enforce the read-only share flag when creating a stream Date: Fri, 20 Nov 2026 06:52:15 +0100 Message-ID: <2026112020-CVE-2026-99749-dc6e@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=2448; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=6HuY7sHDdV1lXn2HtSNRPHdtgYKpxRcQ1o6gRwk3dqo=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/78+5frf+aK3My7Lot8Umpfk3tlzOO/+EpUjEw2LZr 2UftvBndcSyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBE1ixgmO8Rt+8Q//EVS4/f 67Qw0v+fWm59o4RhrnC4dcyJNcd5o7e8+xQ154Njj9Q7dQA= 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: ksmbd: enforce the read-only share flag when creating a stream When a share is read-only, smb2_open() rejects opens that would create or truncate a file. Creating a named stream on an existing file with streams_xattr sets neither O_CREAT nor O_TRUNC, so it passes this check, and smb2_set_stream_name_xattr() then creates the stream. On a Time Machine share, opening a missing AFP_AfpInfo stream also writes one. A user who can write a file at the filesystem level can therefore add streams to it through a read-only share. Do not create a stream or synthesize AFP_AfpInfo when the share is not writable. Existing streams still open normally, and a missing stream opened with FILE_OPEN still returns STATUS_OBJECT_NAME_NOT_FOUND. The Linux kernel CVE team has assigned CVE-2026-99749 to this issue. Affected and fixed versions =========================== Issue introduced in 5.15 with commit e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and fixed in 7.3.5 with commit ece35b45ec17a462cc5947ad4fbc3450657aa55b Issue introduced in 5.15 with commit e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and fixed in 7.4-rc2 with commit 09139429fab3a5114c18d7c15fb161511d4d66c9 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-99749 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/smb/server/smb2pdu.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/ece35b45ec17a462cc5947ad4fbc3450657aa55b https://git.kernel.org/stable/c/09139429fab3a5114c18d7c15fb161511d4d66c9