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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025082239-CVE-2025-38660-19fa@gregkh>
Date: Fri, 22 Aug 2025 18:01:08 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38660: [ceph] parse_longname(): strrchr() expects NUL-terminated string

From: Greg Kroah-Hartman <gregkh@...nel.org>

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

The Linux kernel CVE team has assigned CVE-2025-38660 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.6 with commit dd66df0053ef84add5e684df517aa9b498342381 and fixed in 6.12.42 with commit bb80f7618832d26f7e395f52f82b1dac76223e5f
	Issue introduced in 6.6 with commit dd66df0053ef84add5e684df517aa9b498342381 and fixed in 6.15.10 with commit 3145b2b11492d61c512bbc59660bb823bc757f48
	Issue introduced in 6.6 with commit dd66df0053ef84add5e684df517aa9b498342381 and fixed in 6.16.1 with commit 493479af8af3ab907f49e99323777d498a4fbd2b
	Issue introduced in 6.6 with commit dd66df0053ef84add5e684df517aa9b498342381 and fixed in 6.17-rc1 with commit 101841c38346f4ca41dc1802c867da990ffb32eb

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2025-38660
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	fs/ceph/crypto.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/bb80f7618832d26f7e395f52f82b1dac76223e5f
	https://git.kernel.org/stable/c/3145b2b11492d61c512bbc59660bb823bc757f48
	https://git.kernel.org/stable/c/493479af8af3ab907f49e99323777d498a4fbd2b
	https://git.kernel.org/stable/c/101841c38346f4ca41dc1802c867da990ffb32eb