[ceph] parse_longname(): strrchr() expects NUL-terminated string
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.157, 6.12.42, 6.15.10, 6.16.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
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...
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From dd66df0053ef84add5e684df517aa9b498342381 · fixed in 4b9aee707c4580511983a0998547f3b28514e6a6; From dd66df0053ef84add5e684df517aa9b498342381 · fixed in bb80f7618832d26f7e395f52f82b1dac76223e5f; From dd66df0053ef84add5e684df517aa9b498342381 · fixed in 3145b2b11492d61c512bbc59660bb823bc757f48; From dd66df0053ef84add5e684df517aa9b498342381 · fixed in 493479af8af3ab907f49e99323777d498a4fbd2b; From dd66df0053ef84add5e684df517aa9b498342381 · fixed in 101841c38346f4ca41dc1802c867da990ffb32eb
- Linux Linux
6.6
- KernelLinux
From 6.6.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.42; From 6.13.0 · fixed in 6.15.10; From 6.16.0 · fixed in 6.16.1