CVE-2026-64541VulnerabilityPublished 5 Nov 2026Updated 6 Nov 2026

Red Hat Security Advisory: kernel security update

Affects Linux kernelSource GCVE Database

Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-64541· Critical 9.8

Not known to be exploited · CVSS 9.8 Critical · fixed in Red Hat package updates : patch Linux kernel as a priority.

Data as of 6 Nov 2026, 07:32 UTC

CVSS 3.1 base score

9.8Critical

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA	CVSS 3.1	9.8

Patch: Available – fixed in ce5aa8084329351086894aa34d77e40301d5bd3d, 8145b432136285e01091815b48ceb2dae261f262, 1951bffbc6493ec34cff3956b29d4bc6606904a6 +5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ d7b0e37c1ac152905b18a5b9506179091a35b0b6, < ce5aa8084329351086894aa34d77e40301d5bd3d	Fixed in ce5aa8084329351086894aa34d77e40301d5bd3d
LinuxLinux	Affected ≥ d7b0e37c1ac152905b18a5b9506179091a35b0b6, < 8145b432136285e01091815b48ceb2dae261f262	Fixed in 8145b432136285e01091815b48ceb2dae261f262
LinuxLinux	Affected ≥ d7b0e37c1ac152905b18a5b9506179091a35b0b6, < 1951bffbc6493ec34cff3956b29d4bc6606904a6	Fixed in 1951bffbc6493ec34cff3956b29d4bc6606904a6
LinuxLinux	Affected ≥ d7b0e37c1ac152905b18a5b9506179091a35b0b6, < 647b19e5cc145a2f1f685ae8ff3805a17356888c	Fixed in 647b19e5cc145a2f1f685ae8ff3805a17356888c
LinuxLinux	Affected ≥ d7b0e37c1ac152905b18a5b9506179091a35b0b6, < 472e9d7c0d5b03be3ff91ff941f57da822b031bc	Fixed in 472e9d7c0d5b03be3ff91ff941f57da822b031bc
LinuxLinux	Affected ≥ d7b0e37c1ac152905b18a5b9506179091a35b0b6, < 9d160b35cc34a2ba8229d07651468a7848325135	Fixed in 9d160b35cc34a2ba8229d07651468a7848325135

AI-suggested

Red Hat has released an official kernel update that addresses all listed vulnerabilities. Users should apply the update promptly and reboot their systems for the changes to take effect. Red Hat strongly advises against delaying this update as the kernel's fundamental role means any bug could impact system security. No additional mitigations are specified beyond applying the official patch and rebooting.

Description

This advisory addresses multiple security vulnerabilities in the Linux kernel packages for Red Hat Enterprise Linux 9. The issues include use-after-free bugs, validation errors, race conditions, and memory leaks across various kernel subsystems such as net/smc, sctp, s390/zcrypt, sunrpc, fs/resctrl, openvswitch, and others. These vulnerabilities have been rated as important by Red Hat and require a kernel update and system reboot to mitigate.

Impact

The vulnerabilities affect the Linux kernel, a critical component of the operating system, potentially allowing attackers to exploit use-after-free conditions, race conditions, and improper input validations. These flaws could lead to system crashes, privilege escalation, or denial of service. The advisory rates the overall security impact as important, indicating a high risk if unpatched. No known exploits in the wild have been reported at this time.

CWE-416Use After Free (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #7
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Architecture and Design · Language Selection
Choose a language that provides automatic memory management.
Implementation · Attack Surface Reduction
When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-825Expired Pointer Dereference (opens in a new tab)
Base weakness
The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.
Architecture and Design
Choose a language that provides automatic memory management.
Implementation
When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-787Out-of-bounds Write (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #5
The product writes data past the end, or before the beginning, of the intended buffer.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-366Race Condition within a Thread (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
If two threads of execution use a resource simultaneously, there exists the possibility that resources may be used while invalid, in turn making the state of execution undefined.
Architecture and Design
Use locking functionality. This is the recommended solution. Implement some form of locking mechanism around code which alters or reads persistent data in a multithreaded environment.
Architecture and Design
Create resource-locking validation checks. If no inherent locking mechanisms exist, use flags and signals to enforce your own blocking scheme when resources are being used by other threads of execution.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V1.11.2 (opens in a new tab)
Attack patterns
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions (opens in a new tab)
Leveraging Race Conditions (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-805Buffer Access with Incorrect Length Value (opens in a new tab)
Base weaknessLikelihood of exploit: High
The product uses a sequential operation to read or write a buffer, but it uses an incorrect length value that causes it to access memory that is outside of the bounds of the buffer.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overflow Buffers (opens in a new tab)
SOAP Array Overflow (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

GCVE source: db.gcve.eu
Csaf Category: csaf_security_advisory
Csaf Version: 2.0
Publisher: Red Hat Product Security
Advisory ID: RHSA-2026:95370
Vendor Severity: high
CVE Count: 16
Additional Cves: CVE-2026-68162, CVE-2026-68451, CVE-2026-68452, CVE-2026-72080, CVE-2026-72221, CVE-2026-72222, CVE-2026-74586, CVE-2026-74588, CVE-2026-74752, CVE-2026-80553, CVE-2026-80571, CVE-2026-80584, CVE-2026-89479, CVE-2026-89488, CVE-2026-98403

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Nov 2026, 07:32 UTC

WeaknessesCWE-416, CWE-825, CWE-787 +2

Technical details

References

Community reviews

Related threats