ceph: fix oops due to invalid pointer for kfree() in parse_longname()
Summary
| CVE | CVE-2026-23201 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-02-14 17:15:57 UTC |
| Updated | 2026-09-14 12:17:39 UTC |
| 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 "[email protected]=/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. |
Risk And Classification
Primary CVSS: v3.1 5.5 MEDIUM from [email protected]
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Problem Types: CWE-476
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Operating System | Linux | Linux Kernel | All | All | All | All |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 4b9aee707c4580511983a0998547f3b28514e6a6 c9a129c82ddf82a50b4f8960d2609714ca2dbd26 git | Not specified |
| CNA | Linux | Linux | affected bb80f7618832d26f7e395f52f82b1dac76223e5f 8c9af7339de419819cfc641d551675d38ff99abf git | Not specified |
| CNA | Linux | Linux | affected 101841c38346f4ca41dc1802c867da990ffb32eb e258ed369c9e04caa7d2fd49785d753ae4034cb6 git | Not specified |
| CNA | Linux | Linux | affected 101841c38346f4ca41dc1802c867da990ffb32eb bc8dedae022ce3058659c3addef3ec4b41d15e00 git | Not specified |
| CNA | Linux | Linux | affected 3145b2b11492d61c512bbc59660bb823bc757f48 git | Not specified |
| CNA | Linux | Linux | affected 493479af8af3ab907f49e99323777d498a4fbd2b git | Not specified |
| CNA | Linux | Linux | affected 6.12.42 6.12.70 semver | Not specified |
| CNA | Linux | Linux | affected 6.15.10 6.16 semver | Not specified |
| CNA | Linux | Linux | affected 6.16.1 6.17 semver | Not specified |
| CNA | Linux | Linux | affected 6.17 | Not specified |
| CNA | Linux | Linux | unaffected 6.17 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.70 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.10 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.19 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/bc8dedae022ce3058659c3addef3ec4b41d15e00 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/8c9af7339de419819cfc641d551675d38ff99abf | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/e258ed369c9e04caa7d2fd49785d753ae4034cb6 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/c9a129c82ddf82a50b4f8960d2609714ca2dbd26 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.