Is this bug fixed in the 3.2.0-67.101? This bug should be treated as an urgent security problem. It prevents further kernel updates espacially on firewall machines.
Is this bug fixed in the 3.2.0-67.101?
This bug should be treated as an urgent security problem. It prevents further kernel updates espacially on firewall machines.