What’s Vulnerable › Vulnerabilities
CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname()
- Severity: medium (CVSS 5.5 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.1% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-02-14 · updated 2026-09-14
- Weakness: CWE-476
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.
Affected products
- Linux kernel: from 6.12.42 before 6.12.70; from 6.15.10 before 6.16; from 6.16.1 before 6.18.10; 6.19-rc1, 6.19-rc2, 6.19-rc3, 6.19-rc4, 6.19-rc5, 6.19-rc6 (+2) — fixed in 6.12.70, 6.16, 6.18.10
How to fix
Upgrade to a fixed version: Linux kernel 6.12.70, 6.16, 6.18.10. Check the vendor advisory for mitigations.
References
- https://git.kernel.org/stable/c/8c9af7339de419819cfc641d551675d38ff99abf
- https://git.kernel.org/stable/c/bc8dedae022ce3058659c3addef3ec4b41d15e00
- https://git.kernel.org/stable/c/c9a129c82ddf82a50b4f8960d2609714ca2dbd26
- https://git.kernel.org/stable/c/e258ed369c9e04caa7d2fd49785d753ae4034cb6
Get alerted when CVE-2026-23201 or the next vulnerability affects your stack