From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 CF55113C918 for ; Sat, 14 Feb 2026 16:30:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771086604; cv=none; b=lmyF3htTllZUr2395gsfpRLmv+WBT+wUuLgzYbKjFJhkdYnbq3xZUKWw4gOsNLkixth2Q9PuQNrFDlvCR3a8ZTE7hZe0sl2sL64yMCoNyFTqJZUAdc8c54IvVxwbL0d6960XC8zvfTFmbaWVzh4xtXMgf/Z3PzRZe8PXy0jF/NY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771086604; c=relaxed/simple; bh=OgiDAXDR76HJNHa2LCiGhMPCwO21pOeKS03SQ39LZ/c=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=TN85YkzQOaEIsHmoN+kQn9ESVfV0Mxl++TCZI7vEB1qkGEqSy2pninXv2KLJR86CT7WZ9sgIgswvcK6Q//UDoGGynp58+FGBSKPxkeBj3IXFhrJD8cMcy6cADojqo7KVKrY8PrsFbThYZFwfdJKiBpVdxHm8059q6/0VjTzNTr8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=TFCMybT/; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="TFCMybT/" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 081B4C16AAE; Sat, 14 Feb 2026 16:30:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1771086604; bh=OgiDAXDR76HJNHa2LCiGhMPCwO21pOeKS03SQ39LZ/c=; h=From:To:Cc:Subject:Date:Reply-To:From; b=TFCMybT/o84fCGy90mRFQDYCdfOHklcuOVsrNh44VvOP2XW9ok+dvuFwRVSb1TPCF t+kMGF3IMTN4xYAntFfui5E62tFfyONaBTDb9/eICBcBhEf0dK4+QYxgeqBh7VMreK EtRwYRYcI5t9NWCUczoqM0oizO8046BeMYs7nHkU= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() Date: Sat, 14 Feb 2026 17:28:58 +0100 Message-ID: <2026021436-CVE-2026-23201-4530@gregkh> X-Mailer: git-send-email 2.53.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=3117; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=5A4+Q0MwPeCicfU8Yxu3svxMsCDMt9Er2Ww23WeHSjY=; b=owGbwMvMwCRo6H6F97bub03G02pJDJkTFm2pVGD2KFng4r8wTcW4b8OMNcbbL1bVZbIffbNt8 +v377c4d8SyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBEXloxLJjl+HtuuOXT5dEB zxbs2H3D5ZPw+TsM81PtO1Zb236QXfAxq5EzlUkvMjdrEgA= 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: ceph: fix oops due to invalid pointer for kfree() in parse_longname() This fixes a kernel oops when reading ceph snapshot directories (.snap), for example by simply running `ls /mnt/my_ceph/.snap`. The variable str is guarded by __free(kfree), but advanced by one for skipping the initial '_' in snapshot names. Thus, kfree() is called with an invalid pointer. This patch removes the need for advancing the pointer so kfree() is called with correct memory pointer. Steps to reproduce: 1. Create snapshots on a cephfs volume (I've 63 snaps in my testcase) 2. Add cephfs mount to fstab $ echo "samba-fileserver@.files=/volumes/datapool/stuff/3461082b-ecc9-4e82-8549-3fd2590d3fb6 /mnt/test/stuff ceph acl,noatime,_netdev 0 0" >> /etc/fstab 3. Reboot the system $ systemctl reboot 4. Check if it's really mounted $ mount | grep stuff 5. List snapshots (expected 63 snapshots on my system) $ ls /mnt/test/stuff/.snap Now ls hangs forever and the kernel log shows the oops. The Linux kernel CVE team has assigned CVE-2026-23201 to this issue. Affected and fixed versions =========================== Issue introduced in 6.12.42 with commit bb80f7618832d26f7e395f52f82b1dac76223e5f and fixed in 6.12.70 with commit 8c9af7339de419819cfc641d551675d38ff99abf Issue introduced in 6.17 with commit 101841c38346f4ca41dc1802c867da990ffb32eb and fixed in 6.18.10 with commit e258ed369c9e04caa7d2fd49785d753ae4034cb6 Issue introduced in 6.17 with commit 101841c38346f4ca41dc1802c867da990ffb32eb and fixed in 6.19 with commit bc8dedae022ce3058659c3addef3ec4b41d15e00 Issue introduced in 6.15.10 with commit 3145b2b11492d61c512bbc59660bb823bc757f48 Issue introduced in 6.16.1 with commit 493479af8af3ab907f49e99323777d498a4fbd2b 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-23201 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/ceph/crypto.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/8c9af7339de419819cfc641d551675d38ff99abf https://git.kernel.org/stable/c/e258ed369c9e04caa7d2fd49785d753ae4034cb6 https://git.kernel.org/stable/c/bc8dedae022ce3058659c3addef3ec4b41d15e00