[ceph] parse_longname(): strrchr() expects NUL-terminated string
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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...
From the CVE record · Linux
The Linux kernel’s Ceph parse_longname() function can pass a string that is not guaranteed to be NUL-terminated to strrchr(). The input does not specify what an attacker could achieve or whether exploitation requires network access, authentication, or user interaction.
Anyone running a Linux kernel with the affected Ceph code should check their version; affected versions are not specified.