CVE-2025-38660
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.
Does this matter?
Lower severity and a low EPSS score (0.39%). Track it; it rarely justifies an emergency change on its own.
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...
- CVSS 3.1
- 5.5 MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 0.39% probability · 32th percentile
- CISA KEV
- Not listed
- Affected
- linux/linux kernel
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://git.kernel.org/stable/c/101841c38346f4ca41dc1802c867da990ffb32ebPatch
- https://git.kernel.org/stable/c/3145b2b11492d61c512bbc59660bb823bc757f48Patch
- https://git.kernel.org/stable/c/493479af8af3ab907f49e99323777d498a4fbd2bPatch
- https://git.kernel.org/stable/c/bb80f7618832d26f7e395f52f82b1dac76223e5fPatch
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.