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

Critical 9.8 Published Updated

A missing null terminator in Ceph kernel code causes strrchr to read out of bounds, potentially crashing the system.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2025-38660?

CVE-2025-38660 is a critical vulnerability in Linux kernel, published on 22 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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...

Which versions are affected by CVE-2025-38660?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2025-38660?

Apply the vendor's patch.

Is CVE-2025-38660 being exploited?

There is no known exploitation of CVE-2025-38660 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as AZL-66584, BELL-CVE-2025-38660, DEBIAN-CVE-2025-38660, GHSA-c68j-74mr-g84m, ROOT-OS-DEBIAN-13-CVE-2025-38660, ROOT-OS-UBUNTU-2404-CVE-2025-38660 and 1 more.

Is CVE-2025-38660 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free