Answer in brief
CVE-2025-38660 records a Unknown severity vulnerability in [ceph] parse_longname(): strrchr() expects NUL-terminated string. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=dd66df0053ef84add5e684df517aa9b498342381 <bb80f7618832d26f7e395f52f82b1dac76223e5f || >=dd66df0053ef84add5e684df517aa9b498342381 <3145b2b11492d61c512bbc59660bb823bc757f48 || >=dd66df0053ef84add5e684df517aa9b498342381 <493479af8af3ab907f49e99323777d498a4fbd2b || >=dd66df0053ef84add5e684df517aa9b498342381 <101841c38346f4ca41dc1802c867da990ffb32eb | bb80f7618832d26f7e395f52f82b1dac76223e5f, 3145b2b11492d61c512bbc59660bb823bc757f48, 493479af8af3ab907f49e99323777d498a4fbd2b, 101841c38346f4ca41dc1802c867da990ffb32eb |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Aug 22, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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...
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-38660 records a Unknown severity vulnerability in [ceph] parse_longname(): strrchr() expects NUL-terminated string. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=dd66df0053ef84add5e684df517aa9b498342381 <bb80f7618832d26f7e395f52f82b1dac76223e5f || >=dd66df0053ef84add5e684df517aa9b498342381 <3145b2b11492d61c512bbc59660bb823bc757f48 || >=dd66df0053ef84add5e684df517aa9b498342381 <493479af8af3ab907f49e99323777d498a4fbd2b || >=dd66df0053ef84add5e684df517aa9b498342381 <101841c38346f4ca41dc1802c867da990ffb32eb | bb80f7618832d26f7e395f52f82b1dac76223e5f, 3145b2b11492d61c512bbc59660bb823bc757f48, 493479af8af3ab907f49e99323777d498a4fbd2b, 101841c38346f4ca41dc1802c867da990ffb32eb |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Aug 22, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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...
Quoted source text, attributed separately from HOL analysis.