KernelCare support depends on the exact kernel running on a server, its distribution and architecture, and the maintenance status of that kernel branch. A familiar Linux distribution name or an installed KernelCare agent is not enough to confirm that the current system receives new live patches.
Consult the maintained compatibility information
Use TuxCare’s supported distributions and maintained kernels listing for current coverage, then examine the exact kernel and available fixes in the KernelCare patch catalogue. Match the complete kernel release, including any vendor suffix or special kernel line. Architecture matters as well; a listing for one build must not be treated as coverage for every build of that operating system.
For a specific server, follow our kernel verification procedure. It separates identification of the running kernel, vendor coverage and evidence of patches actually applied. This is also the useful check after changing a kernel or booting into a different version.
Read the lifecycle status
TuxCare’s coverage and lifecycle guidance distinguishes actively patched, paused and retired branches. Existing patches can remain available for a paused or retired branch even though it receives no new patches. Finding an older download therefore does not establish continuing security maintenance.
Where extended lifecycle support is listed, confirm its scope and subscription requirements with the provider. Do not assume that a standard licence extends the support life of the whole operating system or every application installed on it.
Check which system owns the kernel
A virtual machine with its own kernel must be checked against that kernel. A container sharing its host’s kernel cannot independently patch the host by installing KernelCare inside the container. The host administrator is responsible for that layer. A custom or modified kernel also needs explicit confirmation; a similar version number is insufficient.
Coverage can change when you change operating-system versions, architectures or kernel families. Verify the planned destination before a migration, and keep normal operating-system and application maintenance in the plan.
If the catalogue entry is unclear, ask Nuagerie to help assess the relevant service. Include the distribution release, complete running-kernel version, architecture and whether the environment is a host, virtual machine or container. We can use that information to clarify the support question and the administrator or vendor who should resolve it.
