Linux Threat Hunting: ‘Syslogk’ a kernel rootkit found in the wild

Seems to only relate to RHEL 6, or derivatives of, such as CentOS 6. Yes: 6. Which is as EOL as enterprise software gets: <a href="https:&#x2F;&#x2F;access.redhat.com&#x2F;support&#x2F;policy&#x2F;updates&#x2F;errata#Life_Cycle_Dates" rel="nofollow">https:&#x2F;&#x2F;access.redhat.com&#x2F;support&#x2F;policy&#x2F;updates&#x2F;errata#Life...</a>

OpenBSD has removed loadable kernel modules back in 2014; macOS is aggressively moving in the same direction. Meanwhile - is running a Linux system without module support even viable these days?<p>$ du -sh &#x2F;lib&#x2F;modules&#x2F;$(uname -r)<p>294M &#x2F;lib&#x2F;modules&#x2F;5.10.0-15-amd64

&gt; To load the rootkit into kernel space, it is necessary to approximately match the kernel version used for compiling; it does not have to be strictly the same.<p>&gt;&gt; vermagic=2.6.32-696.23.1.el6.x86_64 SMP mod_unload modversions<p>do you know why they say &quot;approximately match&quot;? I thought it had to match exactly so that the kernel accepts to load the module