# Linux Patch Management Policy by Distribution

Canonical: https://patchmanagementpolicy.com/patching/linux-servers/
Last reviewed: 19 Nov 2026

## Linux patch management policy

Linux servers have no single release day; each distribution publishes its own advisories. Red Hat classes flaws on a four-point scale (Low, Moderate, Important, Critical), and Ubuntu runs unattended-upgrades once per day by default. A Linux policy sets its window per distribution. Read 19 Nov 2026.

### Distribution rhythms

Red Hat packages fixes as errata of three types: RHSA for security, RHBA for bug fixes and RHEA for enhancements. Its security classification has four levels. Critical is reserved for flaws “easily exploited by a remote unauthenticated attacker” that lead to system compromise without user interaction; flaws that need authentication, local or physical access, or an unlikely configuration “are not classified as Critical impact” ([Red Hat, severity classification](https://access.redhat.com/security/updates/classification)). A policy that says “critical within X days” must say whose scale it uses, since Red Hat's Critical is narrower than the usual CVSS usage.

Ubuntu installs security updates automatically through the unattended-upgrades package, which is on by default, runs once per day, includes Expanded Security Maintenance when available, and can reboot the system when an update warrants it ([Ubuntu Server documentation](https://documentation.ubuntu.com/server/how-to/software/automatic-updates/)). A repository added later is not considered unless the configuration is changed.

### How one cloud tool treats each distribution

| Distribution | AWS default baseline approval rule | Wait |
|---|---|---|
| Debian Server | Operating system security patches, all listed priorities | None: release dates not reliable in the repositories |
| Red Hat Enterprise Linux | Security patches with severity Critical or Important, plus Bugfix | 7 days after release or update |
| Oracle Linux | Security patches Important or Moderate; Bugfix after 7 days | 7 days |
| SUSE Linux Enterprise Server | Security patches Critical or Important | 7 days |
| Ubuntu Server | Operating system security patches, all listed priorities | None |

Source: AWS Systems Manager, predefined baselines, read 19 Nov 2026. For Amazon Linux 2, the 7 days run from the Updated Date value in updateinfo.xml.

The table shows why one policy number cannot be copied across distributions: the same tool delays one family by a week and none for another, and Moderate-severity RHEL security patches are not in the default baseline.

Cloud-hosted Linux follows [cloud virtual machines](https://patchmanagementpolicy.com/patching/cloud-virtual-machines/), and the steps that apply to every class are on the [process page](https://patchmanagementpolicy.com/process/).

### Window, testing and rollback

Set the window by severity on the distribution's own scale, and keep a separate, shorter path for anything on the CISA Known Exploited Vulnerabilities list. Test on a staging group of each distribution version in use. For kernel fixes without a restart, see [systems that cannot reboot](https://patchmanagementpolicy.com/patching/systems-that-cannot-reboot/); Red Hat's live kernel patches are for selected Important and Critical CVEs only. Package-level rollback depends on the package manager and snapshots, and the sources read here do not document it, so the policy should require a snapshot or image before the change.

### Evidence

- The advisory identifiers applied per host (RHSA numbers, Ubuntu notices).
- The unattended-upgrades log from /var/log/unattended-upgrades.
- Hosts with kernels older than the one installed on disk, listed until restarted.

The verification states are in [verify](https://patchmanagementpolicy.com/process/verify/).

### Sources

- [Red Hat, severity classification](https://access.redhat.com/security/updates/classification), read 19 Nov 2026
- [Red Hat, Explaining Red Hat Errata (RHSA, RHBA, RHEA)](https://access.redhat.com/articles/explaining_redhat_errata), read 19 Nov 2026
- [Ubuntu Server documentation, automatic updates](https://documentation.ubuntu.com/server/how-to/software/automatic-updates/), read 19 Nov 2026
- [AWS Systems Manager, predefined and custom patch baselines](https://docs.aws.amazon.com/systems-manager/latest/userguide/patch-manager-predefined-and-custom-patch-baselines.html), read 19 Nov 2026
- [Red Hat, live kernel patching](https://access.redhat.com/solutions/2206511), read 19 Nov 2026

Last reviewed 19 Nov 2026

### Related pages

- [Patching Systems That Cannot Be Rebooted](https://patchmanagementpolicy.com/patching/systems-that-cannot-reboot/)
- [Step 7: How to Verify Patches Are Installed](https://patchmanagementpolicy.com/process/verify/)
- [Patch Window Table: Deadlines in 12 Frameworks](https://patchmanagementpolicy.com/patch-windows/)
- [Cloud Patch Management: AWS and Azure VMs](https://patchmanagementpolicy.com/patching/cloud-virtual-machines/)
