Multiple Linux kernel vulnerabilities affect Ubuntu LTS releases
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Ubuntu kernel patches multiple vulnerabilities enabling privilege escalation, data breach, and integrity violations across 18.04 ESM through 26.04 LTS.
CERT-FR has published an advisory documenting multiple vulnerabilities discovered in the Linux kernel used across multiple Ubuntu distributions. The affected versions span Ubuntu 18.04 ESM, 20.04 ESM, 22.04 LTS, 24.04 LTS, and 26.04 LTS. These vulnerabilities enable attackers to achieve privilege escalation, compromise data confidentiality, violate data integrity, and bypass security policies.
Ubuntu has released coordinated security updates across 24 separate USN (Ubuntu Security Notice) bulletins published between 24–29 July 2026, addressing over 200 distinct CVEs in the kernel. The kernel vulnerabilities span CVE identifiers from 2022 through early 2026, indicating a backport patching effort across multiple kernel versions and flavors maintained by Canonical.
Defenders must prioritize patching kernel updates on all affected Ubuntu LTS systems. The advisory directs administrators to Ubuntu's official security bulletins for each release, which contain specific CVE identifications, affected kernel versions, and patch guidance. No indication of in-the-wild exploitation is stated in the advisory itself.
Mentioned in this report
Source reporting: https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0954
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,853 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs