CVE-2025-38660

published 22 Aug 2025 · updated 5 Nov 2026

[ceph] parse_longname(): strrchr() expects NUL-terminated string

9.8CriticalCVSS 9.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel bb80f7618832d26f7e395f52f82b1dac76223e5f, Kernel 101841c38346f4ca41dc1802c867da990ffb32eb, Kernel 3145b2b11492d61c512bbc59660bb823bc757f48 and 6 more.

In the Linux kernel, the following vulnerability has been resolved: [ceph] parse_longname(): strrchr() expects NUL-terminated string ... and parse_longname() is not guaranteed that. That's the reason why it uses kmemdup_nul() to build the argument for kstrtou64(); the problem is, kstrtou64() is not the only thing that need it. Just get a NUL-terminated copy of the entire thing and be done with that...

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=dd66df0053ef84add5e684df517aa9b498342381 <bb80f7618832d26f7e395f52f82b1dac76223e5f, >=dd66df0053ef84add5e684df517aa9b498342381 <101841c38346f4ca41dc1802c867da990ffb32eb, >=dd66df0053ef84add5e684df517aa9b498342381 <3145b2b11492d61c512bbc59660bb823bc757f48, >=dd66df0053ef84add5e684df517aa9b498342381 <493479af8af3ab907f49e99323777d498a4fbd2b, >=dd66df0053ef84add5e684df517aa9b498342381 <4b9aee707c4580511983a0998547f3b28514e6a6, =6.6bb80f7618832d26f7e395f52f82b1dac76223e5f, 101841c38346f4ca41dc1802c867da990ffb32eb, 3145b2b11492d61c512bbc59660bb823bc757f48, 493479af8af3ab907f49e99323777d498a4fbd2b, 4b9aee707c4580511983a0998547f3b28514e6a6
linux-kernel: Kernel>=6.16.0 <6.16.1, >=6.6.0 <6.6.157, >=6.7.0 <6.12.42, >=6.13.0 <6.15.106.16.1, 6.6.157, 6.12.42, 6.15.10

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2025-38660 severity on Zeptric[![CVE-2025-38660](https://zeptric.io/badge/cve/CVE-2025-38660.svg)](https://zeptric.io/cve/CVE-2025-38660)