Security updates

Ubuntu is a fixed-release Linux distribution. As such, Ubuntu releases receive security updates during the support window in the form of backported patches. This means that security updates won’t generally introduce new functionality, and we achieve stability by maintaining backward compatibility. Note that some packages in Ubuntu receive feature updates through the Stable Release Update process, but this is independent of security updates. ..

FIXME: this might also be documented elsewhere. It would be good to also reference what LTS and interim releases are.

The level of security support depends on the component in which a package resides (Main, Restricted, Universe or Multiverse). The Ubuntu Security Team prepares security updates for supported Ubuntu releases and works with the community to sponsor community-prepared security updates. The following table lists the security maintenance window for Ubuntu releases. You can read more about the Ubuntu release cycle here.

Support type

Main / Restricted

Universe / Multiverse

Ubuntu Pro required

Interim

9 months

Community support only (9 months)

LTS

5 years

Community support only (5 years)

LTS + ESM infra only

10 years

Community support only (5 years)

LTS + ESM infra and apps

10 years

10 years

LTS + ESM infra and apps + ESM Legacy

15 years

15 years

Ubuntu Pro is a subscription that provides access to several security-focused features and services. You can read more about it in the Ubuntu Pro documenation.

Update Notifications

For Ubuntu Desktop, you receive notifications when new updates are available as part of the update-notifier package. You can also configure automatic updates with the software-properties package (known as Software & Updates in the desktop menu). You can use it to configure the notifications, manage updates, and manage automatic update settings (with more information in the Automatic security updates section below). The update-manager (known as Software Updater in the desktop menu) in turn installs any available updates.

For Ubuntu Server, update-notifier-common provides notifications about pending updates through the Message of the Day (MOTD) upon logging into the system. It is installed by default on Ubuntu 18.04 and later versions. To install it on earlier versions of Ubuntu, you can run the following commands:

sudo apt update
sudo apt -y install update-notifier-common

Delivery

We deliver security updates through special-purpose pockets in the Ubuntu archive. For standard support, we use the security pocket, available from http://security.ubuntu.com/ubuntu with a suite name that follows the RELEASE-security naming convention. For example, the following APT sources configuration in DEB822 format configures the security pocket on the Main and Universe components for Ubuntu 24.04 LTS (Noble Numbat):

Types: deb
URIs: http://security.ubuntu.com/ubuntu/
Suites: noble-security
Components: main universe
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

We deliver security updates available with an Ubuntu Pro subscription through a different Archive pocket. The configuration is detailed in the ESM section.

Vulnerability tracking

The Ubuntu Security Team manages information about vulnerabilities in Ubuntu packages through the Ubuntu CVE Tracker (UCT). UCT imports vulnerability data from various sources, including the CVE Program, allowing you to reference vulnerabilities through CVE IDs. UCT contains information about known vulnerabilities, even when security updates are not yet available. It doesn’t include vulnerabilities under an embargo, as this is a public project, but adds them upon public disclosure. You can find more information and associated data processing tools in the project’s Git repository.

Additionally, you can browse all vulnerability data available in UCT in the CVE reports section of the Ubuntu website.

Ubuntu Security Notices

Upon publication of security updates for packages in the Ubuntu Archive, the Ubuntu Security Team publishes Ubuntu Security Notices (USNs) that contain information about the vulnerability and affected packages. You can browse all Ubuntu Security Notices on the website or subscribe to the Ubuntu Security Announce mailing list to receive email notifications whenever Ubuntu Archive security updates are made available.

Vulnerability knowledge base

We publish detailed technical information on high-impact, publicly disclosed vulnerabilities, including available mitigation steps, in the Vulnerability knowledge base section of the Ubuntu website.

Data feeds

You can obtain information on available security updates in several industry-standard, machine-readable formats: OVAL, OSV, and VEX. These data feeds facilitate the integration of automated patching tools and vulnerability management scanners by incorporating information on the vulnerabilities that each security update addresses, including by referencing the Common Vulnerabilities and Exposures (CVE) enumeration through CVE IDs. The data feeds are freely available for all supported releases and their use is documented in the respective sections below.

ESM

Livepatch

The Canonical Livepatch service provides security fixes for most major kernel security issues without requiring a reboot.

OVAL

OSV

VEX

Automatic security updates

Starting with Ubuntu 18.04 LTS (Bionic Beaver), unattended-upgrades is included in the default Ubuntu Desktop and Server installations to automatically apply security updates daily. You can configure for earlier Ubuntu releases to automatically apply security updates. By default, the system installs security updates after 24 hours and normal updates after 7 days.

For Ubuntu Desktop, you can manage automatic updates through the internal Software & Updates graphical application available in the menu. For Ubuntu Server, or if you choose not to use the graphical application, you can configure updates through a custom new drop-in configuration file in the /etc/apt/apt.conf.d/ directory, basing it off of the original 50unattended-upgrades file located in that same directory. In order for your custom rules to take precedence, ensure that the new configuration file comes after the original file in lexicographic order, by naming it with a higher preceding number (like 60custom-unattendeed-upgrades). The original config contains explanations for each option available for modification. Through a new configuration file, you can adjust more advanced options, such as enabling automatic reboot when needed, setting the automatic reboot time, and configuring logging capabilities.

Warning

Editing the original configuration file is highly discouraged as it can create problems after a system upgrade. If the configuration file is updated from the original defaults, it will cause issues if it was modified beforehand. Drop-in files are an alternative designed to solve these types of issues.

You can also enable/disable automatic updates through the command terminal without editing the configuration file by running the following command:

sudo dpkg-reconfigure unattended-upgrades

Note

Automatic updates through unattended-upgrades are only configured by default for archive repositories (as well as ESM if Ubuntu Pro is enabled). To configure automatic updates for third party repositories and PPAs, you must create a new drop in file in the /etc/apt/apt.conf.d/ directory.

For example, in order to enable unattended upgrades for the hypothetical ubuntu-security/demo PPA, run the following command:

echo 'Unattended-Upgrade::Allowed-Origins { "LP-PPA-ubuntu-security-demo:${distro_codename}"; };' | sudo tee /etc/apt/apt.conf.d/90-unattended-ubuntu-security-ppa.conf

The new file will configure the Allowed-Origins option, which will be added with the pre-existing Allowed-Origins configuration in the 50unattended-upgrades file. As the Allowed-Origins option is a list option, it will not replace the option in files with lower priority, allowing the creation of a separate configuration file for each PPA if needed, which will be added together.

For more information, you can read the manual page.

The operations of unattended-upgrades are logged in /var/log/unattended-upgrades/unattended-upgrades.log.