Skip to content
Fencer Intel
medium 5.5

CVE-2026-23201 json

ceph: fix oops due to invalid pointer for kfree() in parse_longname()

published 8mo ago modified last mo. also EUVD-2026-5844

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 2%
public exploits
0
none known

Summary

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.

Patch / fix

  • Linux Linux 6.12.70, 6.16, 6.17, 6.18.10, 6.19
  • linux Debian 13 6.12.73-1
  • linux Debian 14 6.18.10-1

debian advisories DEBIAN-CVE-2026-23201

  • cephfs SLE Module for Legacy 15 SP7 1.0-150700.15.7.1
  • kernel-rt Real Time Module 15 SP7 6.4.0-150700.7.37.2
  • kernel-syms-rt Real Time Module 15 SP7 6.4.0-150700.7.37.1
  • kernel-source-rt Real Time Module 15 SP7 6.4.0-150700.7.37.2
  • kernel-rt Linux Micro 6.2 6.12.0-160000.28.1
  • kernel-64kb Linux Micro 6.2 6.12.0-160000.28.1
  • kernel-source Linux Micro 6.2 6.12.0-160000.28.1
  • kernel-default Linux Micro 6.2 6.12.0-160000.28.1

suse advisories SUSE-SU-2026:5111-1SUSE-SU-2026:1573-1SUSE-SU-2026:21237-1SUSE-SU-2026:21230-1SUSE-SU-2026:21255-1SUSE-SU-2026:21123-1

  • kernel-rt openSUSE Leap 16.0 6.12.0-160000.28.1
  • dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.28.1
  • kernel-64kb openSUSE Leap 16.0 6.12.0-160000.28.1
  • kernel-syms openSUSE Leap 16.0 6.12.0-160000.28.1
  • kernel-azure openSUSE Leap 16.0 6.12.0-160000.28.1
  • kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.28.1
  • kernel-source openSUSE Leap 16.0 6.12.0-160000.28.1
  • kernel-default openSUSE Leap 16.0 6.12.0-160000.28.1

opensuse advisories openSUSE-SU-2026:20572-1

Is CVE-2026-23201 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-23201 updated

kernel: ceph: fix oops due to invalid pointer for kfree() in parse_longname()

  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.