An “Unknown Kernel” or “Unsupported Kernel” message means that live-patch coverage for the running kernel needs investigation. Installing KernelCare does not make an unsupported kernel supported, and an active licence does not prove that patches have been applied. The message alone also does not establish that the server is compromised or that a particular vulnerability affects it.
Confirm what the message refers to
Keep the exact error and the time it appeared, then follow our kernel compatibility and patch verification procedure. Compare the running kernel, distribution, architecture and current catalogue entry. Do not rely only on the operating-system family or a kernel package installed on disk.
A newly released build may not yet appear in the catalogue. An older branch may no longer receive new live patches. A custom kernel or a container sharing another system’s kernel needs a different assessment. None of these cases should be resolved by assuming that every new kernel is safe or that an old patch download proves ongoing coverage.
Choose a response for the actual cause
- Exact build not listed: ask the administrator or TuxCare to confirm its status against the current patch catalogue. There is no universal waiting period after which coverage can be assumed.
- Paused or retired branch: review the published lifecycle status and plan a supported destination or an explicitly confirmed support arrangement.
- Container environment: involve the host administrator. Installing a kernel-patching agent inside a container does not independently patch the shared host kernel.
- Expected support but an error remains: have the administrator check the agent version, licence, patch source, connectivity and module-loading errors. If a signing-key error appears, consult TuxCare’s Secure Boot and module-signing guidance.
Preserve a controlled maintenance path
Do not silence the warning or force patch loading simply to clear the alert. A change of kernel, agent or boot configuration should follow a reviewed maintenance plan, including recovery access and checks of the services that depend on the server. Changing to another kernel may require a reboot; live patching does not eliminate every maintenance restart.
If an urgent vulnerability is involved, ask the responsible administrator to assess the applicable advisory and available remediation now, rather than waiting only for the agent’s message to change.
Contact Nuagerie with the error and verification results for the relevant service. Include whether it began after an update or reboot. This helps distinguish a compatibility question from a configuration or maintenance issue without making unnecessary changes.