LiveActive security incident?Get immediate response
CVE Record

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

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

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A Linux Ceph filesystem parser may read beyond supplied data because it treats that data as a properly terminated string. This can threaten confidentiality, integrity, and availability according to the supplied 9.8 CVSS assessment. Practical exposure depends on whether a system uses the affected Ceph code and whether its kernel includes a corrective commit.

Executive priority

Treat as an urgent patch-validation issue for Ceph-dependent infrastructure because the supplied severity is critical. Accelerate inventory and vendor confirmation, but do not represent exploitation as observed. Systems without Ceph filesystem use are lower investigative priority, subject to confirmation.

Technical view

Ceph parse_longname() passed a buffer not guaranteed to be NUL-terminated to strrchr(). The resolution creates a NUL-terminated copy of the entire input before parsing. The bundle identifies four Linux stable commits, but does not clearly map each affected release to its corresponding fixed release.

Likely exposure

Prioritize Linux systems using Ceph filesystem functionality. The bundle marks Linux releases 6.6, 6.12.42, 6.15.10, 6.16.1, and 6.17 as affected, but also contains an unexplained "0" and incomplete range semantics. Distribution kernels may contain backports, so version numbers alone are insufficient.

Exploitation context

The supplied CVSS vector describes network reachability, low complexity, no privileges, and no user interaction. However, CISA KEV status is false, and the bundle provides no evidence of active exploitation or a public exploit. Treat real-world exploitability as unconfirmed.

Researcher notes

The defect is a string-boundary error involving strrchr() and non-NUL-terminated input. No CWE is supplied. The affected-version data is ambiguous and repeats one commit hash under unaffected entries. Validate ancestry and distribution backports against the four stable commits before declaring a host vulnerable or fixed.

Mitigation direction

  • Apply a vendor-supported kernel update containing the relevant Linux stable correction.
  • Check distribution advisories for backported fixes before relying on upstream version numbers.
  • Reduce unnecessary Ceph filesystem exposure until affected systems are updated.
  • Follow vendor guidance where packaged kernel status remains unclear.

Validation and detection

  • Inventory systems using Ceph filesystem functionality and record exact kernel package builds.
  • Check package changelogs for the four corrective commit identifiers.
  • Confirm kernel provenance and vendor backport status, not only the reported release number.
  • After updating, verify the corrected kernel is running and Ceph filesystems operate normally.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-38660 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2025-38660Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxdd66df0053ef84add5e684df517aa9b498342381, dd66df0053ef84add5e684df517aa9b498342381, dd66df0053ef84add5e684df517aa9b498342381, dd66df0053ef84add5e684df517aa9b498342381unaffected
LinuxLinux6.6, 0, 6.12.42, 6.15.10, 6.16.1, 6.17affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.