CVE-2026-80844VulnerabilityPublished 2 Oct 2026Updated 29 Oct 2026

Red Hat Security Advisory: kernel security update

Affects Linux kernelSource GCVE Database

Compare

Not known to be exploited.

Data as of 29 Oct 2026, 07:26 UTC

Severity

High

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 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

AI-suggested

Red Hat has released an official security update that fixes this vulnerability. Users should apply the kernel update provided in the advisory for Red Hat Enterprise Linux for ARM 64 version 10. A system reboot is required for the update to take effect. Red Hat strongly advises against delaying the update to avoid exposure to potential risks. Detailed update instructions are available in the Red Hat knowledge base article referenced in the advisory.

Description

A security update for the Linux kernel in Red Hat Enterprise Linux for ARM 64 addresses a vulnerability identified as CVE-2026-80844. The flaw involves improper validation of the routing header segments_left in the xfrm ah6 component of the kernel. Red Hat has rated this update as important and recommends applying the patch promptly. The update requires a system reboot to take effect. This kernel update is part of the NVIDIA for RHEL 10 release and includes additional changes documented in the release notes.

Impact

The vulnerability affects the Linux kernel's handling of routing headers, which could impact system security if exploited. Red Hat classifies the security impact as important, indicating a high severity level. No known exploits in the wild have been reported. Because the kernel is central to system operation, any flaw can have significant security implications.

Summary

The vulnerability CVE-2026-80844 affects the Linux kernel's xfrm ah6 module, specifically due to insufficient validation of the routing header's segments_left field. This could potentially lead to security issues within the kernel, which is a critical component of the operating system. Red Hat has issued a security advisory with an update for the kernel packages in Red Hat Enterprise Linux for ARM 64 (aarch64) version 10, incorporating a fix for this vulnerability. The advisory emphasizes the importance of kernel updates due to the kernel's fundamental role in system security. The update is part of the NVIDIA for RHEL 10 kernel release 6.12.0-259.28.el10nv.

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).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 29 Oct 2026, 07:26 UTC

Public exploits and detectionGitHub proofs of concept

WeaknessesCWE-805

Technical details

References

Community reviews

Related threats