Red Hat Bugzilla – Bug 448380
Wrong capget/capset version 2 usage. Possible memory corruption.
Last modified: 2016-07-26 19:46:56 EDT
Description of problem:
Squid uses getcap/setcap kernel interface, but don't
check version. New kernels uses array of structures to
stora data. Squid uses old interface style. This may
(really detected) lead to memory corruption.
Version-Release number of selected component (if applicable):
kernel >= 2.6.25.
Steps to Reproduce:
1. Run squid under valgrind or ef.
2. Sometimes it crashes without this tools.
Crash or tool warning.
Corrert usage of new interface.
Patch is ready.
Obsoletes not-so-correct squid-3.0.STABLE5-bad_allocation patch.
May be use libcap for this?
Created attachment 306657 [details]
try to user new capget/capset interface.
Just moments before this bug report was filed, I changed the patch to the
upstream one, see http://www.squid-cache.org/bugs/show_bug.cgi?id=2350
If you think that even this one is wrong, please try to send it to the upstream
It seems, that both patches solves the problem.