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=1795100768; b=3iDVsfvemk7CiSFiyS4mBPY2G1O7Ke/Niaed7lIvQmNvGAz5llBNPCGy0SMVIpZuBJ+i liKZ/9p2tAQPn3gCtpo++Y38mbeDo8bTepP7kAMFxHSzGoGa3Moa66QYfUfIVDU+Z4r7m UNSOVdIKWpQOFXi/18j3i2QBWP8Jw7GDYC1X6waZGT3jrr68vlWWk/DVHKmZ4pSSADcK/ +kzHLVkaFwdmLenEng+FJHOQEIYqjQ2ERMdiRguMB6hbeJEfYIR2TgHqtnTuTeUHxQSJU rgBEuFaqDAUQETB9aFzHNPFqViISZTD9IAW6Wz3PXYa+9FE88C8HHmd3NZU1Za/DHWg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795100768; 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=uRp21CVxwwYLYoyQkNyBqcVhd9lPnq0J0MDJr255C4A=; b=kRNnJ6mDMi0/VR4lkIKcreuUIPd5la3KHJuoCOxWvkWAuO545hi5J5SyObc76JPfPxSq /sPRMKz8ceKNlE2dsYciaCmevn8f9AFiqwGEaGK42lbHH7LL/qbzXrJgq75uc1CBMPM6k +gyhxn6jfJlD9K0NmPEctjemxumwusRSwvjlxp+zBUFz68ZXQtoIHfpbpXDQkk1WcgVO7 AIB763oHZHXvlqXv/x29WigPkMrwSV59eCcKHA9UmtX5KZpjSyMkW9avu5b7JYxqCzoNK SG9uXhkKjH45AFcQ5gdn+4uh1NYrisGqgC5zf3//KpQHEJlCqh6QAUWmktdsfWUFdpw== 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=mjz9JoCe; 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 41657606A326 for ; Thu, 19 Nov 2026 15:06:08 +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=mjz9JoCe Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4ABC21F000C4; Thu, 19 Nov 2026 15:06:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795100768; bh=uRp21CVxwwYLYoyQkNyBqcVhd9lPnq0J0MDJr255C4A=; h=From:To:Cc:Subject:Date:Reply-To; b=mjz9JoCe3ieWoOFDctyYXaw7bwf9PJ1eR4I2eqWZcFK1z5/BrEMtXkhCc34mZ+XwL CkbpwKqWzAM13nNMmIXa23yF2rzKloXsidCRgspj2W+08qxaFlGeqYxxnA6ke+YeSb +5rpMfuPnY4JFPR8QVfB3dz7pdHtrvQR7eTM4ybM= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99548: smb: client: fix early procfs exposure race Date: Thu, 19 Nov 2026 15:27:26 +0100 Message-ID: <2026111925-CVE-2026-99548-c2d9@gregkh> X-Mailer: git-send-email 2.56.0 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=3565; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=lRSFO1WnTOMG6P6B7xHq35K4iipZWxTnlgX8zllqpRs=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/2WYePuvv99fJ4NL2Rc6L3vuyBl0oXP3uivYMpwvuK +6vWtHN3BHLwiDIxCArpsjyZRvP0f0VhxS9DG1Pw8xhZQIZwsDFKQATeaLEMD97GfuV0okTQ3+p iSgE3tHyZHhUXscwPyE+Mrpec+H912vrzVeztR9um/S/GwA= 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: smb: client: fix early procfs exposure race Currently, init_cifs() calls cifs_proc_init() near the beginning of the function, before INIT_LIST_HEAD, leading to a momentarily uninitialized, but exposed, procfs. If a userspace process reads this empty procfs, iterating over a zeroed list_head leads to a NULL pointer dereference and a kernel oops/panic. For example, if a delay is added between cifs_proc_init() and INIT_LIST_HEAD, and a userspace process is polling /proc/fs/cifs/DebugData, the following oops occurs: BUG: kernel NULL pointer dereference, address: 0000000000000608 Oops: Oops: 0000 [#1] SMP PTI CPU: 0 UID: 0 PID: 3477 Comm: cat Not tainted 7.3.0-02212-g4df4d2a577db-dirty #6 PREEMPT(lazy) RIP: 0010:cifs_debug_data_proc_show+0x103/0xd80 [cifs] Call Trace: ? seq_read_iter+0x86/0x400 ? seq_read_iter+0x86/0x400 seq_read_iter+0x183/0x400 proc_reg_read_iter+0x62/0x90 copy_splice_read+0x215/0x310 splice_file_to_pipe+0xec/0x1c0 do_splice+0x4b8/0x780 __se_sys_splice+0x18f/0x250 do_syscall_64+0x109/0x330 entry_SYSCALL_64_after_hwframe+0x77/0x7f Fix this by moving cifs_proc_init() down in init_cifs(), ensuring it runs only after all internal lists, locks, counters, and workqueues are fully ready, but before registering the filesystem. Update the error cleanup ladder and exit_cifs() to maintain proper LIFO order. The Linux kernel CVE team has assigned CVE-2026-99548 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.12.117 with commit cfaec5094017bd9d41a0572325ec2cec4f7d5e31 Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.18.61 with commit 4d6e1b44d1fbfa70b045a670b18200dc4824226b Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 7.3.2 with commit 31209411c4f98158b41508b7f90583e8cf5d6076 Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 7.4-rc1 with commit 7b1afb631395c958993cda4631002258ef4151ea 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-99548 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/client/cifsfs.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/cfaec5094017bd9d41a0572325ec2cec4f7d5e31 https://git.kernel.org/stable/c/4d6e1b44d1fbfa70b045a670b18200dc4824226b https://git.kernel.org/stable/c/31209411c4f98158b41508b7f90583e8cf5d6076 https://git.kernel.org/stable/c/7b1afb631395c958993cda4631002258ef4151ea