CVE-2025-38660
[ceph] parse_longname(): strrchr() expects NUL-terminated string
Reported by linux · Published August 22, 2025
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...
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel6.12-modules-extra-common | Amazon Linux | 1:6.12.46-66.121.amzn2023 |
| kernel6.12-libbpf-devel | Amazon Linux | 1:6.12.46-66.121.amzn2023 |
| perf6.12 | Amazon Linux | 1:6.12.46-66.121.amzn2023 |
| kernel6.12 | Amazon Linux | 1:6.12.46-66.121.amzn2023 |
| python3-perf6.12 | Amazon Linux | 1:6.12.46-66.121.amzn2023 |
| kernel6.12-libbpf | Amazon Linux | 1:6.12.46-66.121.amzn2023 |
| kernel6.12-devel | Amazon Linux | 1:6.12.46-66.121.amzn2023 |
| kernel6.12-headers | Amazon Linux | 1:6.12.46-66.121.amzn2023 |
| kernel6.12-tools | Amazon Linux | 1:6.12.46-66.121.amzn2023 |
| kernel6.12-tools-devel | Amazon Linux | 1:6.12.46-66.121.amzn2023 |
| kernel6.12-libbpf-static | Amazon Linux | 1:6.12.46-66.121.amzn2023 |
| kernel-livepatch-6.12.46-66.121 | Amazon Linux | 1:1.0-0.amzn2023 |
1 more packages have a fixed version. See every fix in Lookup.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | dd66df0053ef84add5e684df517aa9b498342381, dd66df0053ef84add5e684df517aa9b498342381, dd66df0053ef84add5e684df517aa9b498342381 |
| Linux | Linux | 6.6, 0, 6.6.157 |
| amazon:2023 | kernel6.12-modules-extra-common | 0 |
| amazon:2023 | kernel6.12-libbpf-devel | 0 |
| amazon:2023 | perf6.12 | 0 |
| amazon:2023 | kernel6.12 | 0 |
| amazon:2023 | python3-perf6.12 | 0 |
| amazon:2023 | kernel6.12-libbpf | 0 |
| amazon:2023 | kernel6.12-devel | 0 |
| amazon:2023 | kernel6.12-headers | 0 |
| amazon:2023 | kernel6.12-tools | 0 |
| amazon:2023 | kernel6.12-tools-devel | 0 |
| amazon:2023 | kernel6.12-libbpf-static | 0 |
| amazon:2023 | kernel-livepatch-6.12.46-66.121 | 0 |
| Linux | Linux | *, 6.6.157, 6.16.1 |
| amazon:2023 | kernel6.12-modules-extra | 0 |
| linux | linux_kernel | 6.6, 6.6, 6.6 |
| amazon:2023 | bpftool6.12 | 0 |
Timeline
- Aug 22, 2025 Coalition ESS Score (7 in total, the first dated here)
- Aug 22, 2025 CVE Published
- Aug 23, 2025 EPSS Score (30 in total, the first dated here)
- Oct 12, 2025 PoC Published (10 in total, the first dated here)
- Dec 15, 2025 Security Advisory (222 in total, the first dated here)
- Mar 29, 2026 Distribution Patch (174 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-38660
vulnetix vdb fixes CVE-2025-38660
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38660/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart