Behind the Scenes at KernelCare: How We Test Patches Before Release - TuxCare

Behind the Scenes at KernelCare: How We Test Patches Before Release

KernelCare Team

October 23, 2020

KernelCare Update

Behind the Scenes at KernelCare: How We Test Patches Before Release

Testing is essential for any software update including patches, but it’s even more essential when changes are made to critical infrastructure that powers revenue-impacting services. Release of security updates that are not thoroughly tested may result in kernel crashes, operating system reboots, system- or service-level failures – some of these aftermaths are critical and some just unpleasant, but all of them can hurt your business and service-level agreements. KernelCare has a strict testing process every patch must go through before it’s deployed to production, and this article details how we ensure customer infrastructure reliability and uptime after patch deployments.

 

Contents:

  1. Patching Delays are Risky
  2. KernelCare Development and Testing
  3. KernelCare’s Four Types of Tests
  4. Conclusion

 

Patching Delays are Risky

Patching Delays are Risky

It’s essential that all software including the Linux kernel is patched when developers release a security update. It’s even more critical to patch as soon as possible when a vulnerability is published with exploit code. The longer you allow servers to stay unpatched, the greater the risk of being the next large data breach victim. It’s not uncommon for administrators to test and wait for a scheduled date before patching. Within this timeframe, an attacker could scan the server, find the vulnerability and exploit it.

 

Leaving patch management to KernelCare eases much of the overhead for administrators, but our clients need the reassurance that proper testing is done before allowing a third party to deploy to critical infrastructure. KernelCare’s patching solutions go through rigorous testing before deployment to our client servers. Our testing alleviates much of the administrative overhead in large organizations so that you no longer need several machines with the various vendor operating systems installed to ensure a clean, bugless patching experience.

 

 

KernelCare Development and Testing

KernelCare Development and Testing

Buggy code can cause several issues including introduction of new vulnerabilities. An example of why it’s so important to test patches before deployment is the discovery of a trivially exploitable vulnerability introduced in May 2020. The patch named Huawei Kernel Self Protection was supposed to offer a series of security-hardening options for the Linux kernel. Instead, it opened the operating system to possible backdoors, offered no threat-level programming, and allowed for disclosure of kernel memory. Because the patch was tested, the Linux team was able to stop it from weakening the security of the kernel. This is one example of why it’s critical to test patches before they’re installed, and KernelCare performs a number of testing types before deployment to our client servers.

 

To help our customers understand the high-level testing we require from our teams, we’ve detailed the process below.

 

  1. We provision a bare-metal physical server or a virtual machine with the target operating system. If the patch for specific CVE (Common Vulnerability Exposures) is for a specific hardware component (e.g. a CPU vulnerability), we provision the corresponding hardware component on the server. For a kernel-based virtual machine (KVM), we will provision nested virtual machines and necessary hardware features.
  2. We pull the kernel that will be used for testing from the vendor and install it on our provisioned test server.
  3. Reboot the server with the newly installed kernel.
  4. We install KernelCare in the same way a customer would. We publish the instructions here.
  5. Execute the KernelCare patching command ($ /usr/bin/kcarectl –update).
  6. Load kernel modules created for the patch.
  7. Validate and test all changed functionalities for the module. 
  8. If exploit code is available, we use this code to reproduce it on the server and test that patches remediate the vulnerability.
  9. Run our four tests (see below).
  10. If patches pass our testing, we deploy them to production.
  11. If tests are unsuccessful, we analyze logs to find the cause of failure, remediate the issue, and then repeat these steps again until patches pass our tests.

 

 

KernelCare’s Four Types of Tests

KernelCare’s Four Types of Tests

Thorough testing is critical for successful deployments, and we know that bugs impact our customers. We have four tests that run simultaneously for each kernel to ensure patches don’t cause critical issues. 

 

Before any patch is deployed, it goes through the following automated tests depending on how fast we need these patches in production and the critical level of the vulnerability:

 

  1. We apply our patches to the running kernel and then unpatch it to test rollbacks. This process takes about 10 minutes per kernel.
  2. We apply our patches and then perform a subset of tests from the Linux Test Project (LTP) test suite which add some load to the operating system. This test takes about 15 minutes per kernel.
  3. The same as 2. but with the full set of LTP tests. This test is a thorough 4 hour per kernel process that includes:
    1. Filesystem stress test
    2. Storage I/O test
    3. Memory management stress test
    4. IPC stress test
    5. Scheduler test
    6. Commands functional verification tests
    7. System call functional verification tests
    8. etc
  4. LTP extra. This test is a high-load test with continuous patching and unpatching throughout the test. This test takes 4 hours per kernel.

 

Conclusion

In order to provide our clients with a stable and reliable patching service – the one you can rely onand even forget that it exists on your servers – we test each patch on each affected kernel for at least 4 hours/kernel and only release patches when we are 100% sure they will not disturb your operations. With KernelCare, administrators can not only patch their systems with no reboot required, but they also know that these patches are thoroughly tested before installation.

Stay in the Loop

Resources

State of Enterprise Linux Cybersecurity ... Read More State of Enterprise Linux Cybersecurity ...
Dangerous remotely exploitable vulnerability ... Read More Dangerous remotely exploitable vulnerability ...
Securing confidential research data ... Read More Securing confidential research data ...
State of Enterprise Vulnerability Detection ... Read More State of Enterprise Vulnerability Detection ...
Demand for Rapid Risk Elimination for ... Read More Demand for Rapid Risk Elimination for ...
TuxCare Free Raspberry Pi Patching Read More TuxCare Free Raspberry Pi Patching