Bug 2390343 (CVE-2025-38660) - CVE-2025-38660 kernel: [ceph] parse_longname(): strrchr() expects NUL-terminated string
Summary: CVE-2025-38660 kernel: [ceph] parse_longname(): strrchr() expects NUL-termina...
Keywords:
Status: NEW
Alias: CVE-2025-38660
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-08-22 17:01 UTC by OSIDB Bzimport
Modified: 2025-08-25 09:23 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-08-22 17:01:27 UTC
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...


Note You need to log in before you can comment on or make changes to this bug.