Red Hat patches scores of Linux kernel flaws
CERT-FR advisory lists over 20 Red Hat Security Advisories patching more than 100 Linux kernel CVEs enabling RCE, privilege escalation and DoS.
Sourcecert.cyber.gouv.fr — open the original
What to check
- Applies to
- The 40 CVEs named below. Whether you run an affected version is not assessed: check the versions the source lists.
- Exploitation
- No exploitation in the wild and no public exploit is recorded for the CVEs named.
CERT-FR has published an advisory consolidating numerous Red Hat Security Advisories (RHSA) issued between October 23 and October 30, 2026, addressing a large batch of vulnerabilities in the Red Hat-maintained Linux kernel. The affected products span nearly the entire current Red Hat Enterprise Linux portfolio (versions 6 through 10, across x86_64, aarch64, ppc64le and s390x architectures), CodeReady Linux Builder, and multiple versions of OpenShift Container Platform (4.12 through 4.22) across all supported architectures, reflecting how deeply the kernel component is embedded in Red Hat's product line.
The vulnerabilities collectively enable a range of impacts including remote arbitrary code execution, local and remote privilege escalation, remote denial of service, information disclosure, data integrity compromise, security policy bypass, and server-side request forgery (SSRF). No single root cause or component is called out; this is a rollup of fixes accumulated across upstream kernel maintenance and backported into Red Hat's kernel builds. The advisory does not indicate that any of these flaws are being actively exploited in the wild — it is a standard patch-availability notice directing administrators to the referenced RHSA bulletins for remediation.
Defenders running any Red Hat Enterprise Linux, CodeReady Linux Builder, or OpenShift Container Platform deployment should treat this as a routine but broad patching cycle: identify which of the listed RHSAs apply to their installed kernel version and architecture, and apply updates according to standard change-management processes. Given the volume of CVEs and the presence of remote code execution and privilege escalation among the impacts, prioritization should follow each organization's exposure (e.g., internet-facing or multi-tenant kernels, OpenShift worker nodes) rather than treating all CVEs as equally urgent.
Mentioned in this report
Source reporting: https://www.cert.cyber.gouv.fr/avis/CERTFR-2026-AVI-1431
Free public brief. Slack alerts on the vendors you run come with the paid plans, and a new account gets three days of them, no card.
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 live profiles of the CVEs it names. The paid plans add the security research and news reporting the free tier leaves out.
It sits in a corpus of 16,445 reports from 149 sources, 666 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. Slack alerts are a paid-plan feature: name the vendors you run and Slack hears about the reports that touch them, not the rest of the week's. Nothing is charged unless you subscribe.
Create a free account What it costs