4 ms·
It is indeed compiled with CONFIG_KEYS=y. Does this protect me against this issue? I'm not sure what this means.
by Maran 11y ago
It is indeed compiled with CONFIG_KEYS=y. Does this protect me against this issue? I'm not sure what this means.
- baghira 11y agoNo, the bug is in the kernel keyring facility, so if I'm not mistaken compiling with CONFIG_KEYS=n option should protect you (I haven't tested though). As for the /proc/kallsyms, I honestly don't know how come you only get zeroes. EDIT: The obvious question I should have asked is which distro you are running. Also, as others have pointed out, hoping that the attacker can't read kallsyms from the machine he's attacking is not really a good defense plan.
- Maran 11y agoI'm running Ubuntu 14.04 which should be affected. I just hoped it would be harder without having the correct kallsyms version. It seems I will have no options except to reboot my cluster :)