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 dd66df0053ef84add5e684df517aa9b498342381 before 4b9aee707c4580511983a0998547f3b28514e6a6; from dd66df0053ef84add5e684df517aa9b498342381 before bb80f7618832d26f7e395f52f82b1dac76223e5f; from dd66df0053ef84add5e684df517aa9b498342381 before 3145b2b11492d61c512bbc59660bb823bc757f48; from dd66df0053ef84add5e684df517aa9b498342381 before 493479af8af3ab907f49e99323777d498a4fbd2b; from dd66df0053ef84add5e684df517aa9b498342381 before 101841c38346f4ca41dc1802c867da990ffb32eb
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.
Printed from infosecsignals.com. Every record links back to the agency that published it.
Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.