Skip to main content

Linux Kernel CVE-2026-98096

| EUVDEUVD-2026-86926 HIGH
2026-09-25 Linux GHSA-qgrh-x7hc-r5h3
7.4
CVSS 3.1 · Vendor: Linux
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach SRv6 segment endpoint over network
  2. Delivery
    Craft IPv6 packet with ext header before SRH
  3. Exploit
    ipv6_srh_rcv leaves negative network offset
  4. Execution
    Forwarding passes offset as unsigned length
  5. Persist
    OOB memcpy corrupts kernel memory
  6. Impact
    Kernel crash / denial of service

Vulnerability Assessment

Exploitation Conditions

Requires the target kernel to be built with SRv6 support (CONFIG_IPV6_SEG6) and configured to act as a Segment Routing endpoint that processes an SRH with segments_left > 0. The trigger is a crafted IPv6 packet in which the SRH is preceded by another extension header (such as a Hop-by-Hop options header), so that skb_network_offset() stays negative; exploitation manifests when the packet is routed via ip6_route_input (breaking BPF/C flow dissection) or forwarded via ip6_forward / redirected via act_mirred (negative offset used as unsigned length in sch_fragment or neighbour output → OOB memcpy). Limiting factors: SRv6 endpoint processing is not enabled by default and is rare outside telco/datacenter deployments, and the packet must be specifically structured (AC:H), though no authentication or user interaction is needed.

Impact

This is a genuinely network-facing memory-safety bug, unlike the many local-only Linux kernel flaws mislabeled as network-exploitable. The CVSS vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H, base 7.4) is largely defensible here: an off-path attacker can send a crafted IPv6 packet carrying a Segment Routing Header (SRH) preceded by another extension header (e.g., Hop-by-Hop options) to a host acting as an SRv6 segment endpoint, so AV:N/PR:N/UI:N hold, and AC:H reflects the requirement that SRv6 processing be configured and the packet be specifically structured. C:N is correct - the description details OOB memcpy / buffer overflow and broken flow dissection, i.e. corruption and crash, not information disclosure; I would temper NVD's I:H toward I:L since the primary observed effect is a crash/DoS from passing a negative offset as an unsigned length, though controlled corruption is plausible. No EPSS score, no CISA KEV entry, and no public exploit are present in the input, so this is not evidence of active exploitation. The dominant limiting factor is deployment: SRv6 segment-endpoint processing is a niche telco/datacenter feature rarely enabled on general-purpose systems, which sharply narrows the real-world attack surface despite the network vector. Net assessment: a real, verify-and-patch-if-you-run-SRv6 issue rather than a broad emergency.

Exploit ScenarioDerived

A host is configured as an SRv6 segment endpoint (CONFIG_IPV6_SEG6, processing SRH with segments_left > 0). A remote attacker sends an IPv6 packet whose SRH is preceded by a Hop-by-Hop options header, causing skb_network_offset() to remain negative; when the packet is routed and forwarded (ip6_forward or act_mirred redirect), the negative offset is treated as an unsigned length, triggering an out-of-bounds memcpy that corrupts memory or crashes the kernel. No public proof-of-concept is identified at time of analysis, and the AC:H rating reflects the required SRv6 configuration and precise packet layout.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 25, 2026

Out-of-bounds memory access in the Linux kernel's IPv6 Segment Routing (SRv6) receive path can be triggered by remote, unauthenticated attackers who send a crafted IPv6 packet containing a Segment Routing Header (SRH) with segments_left > 0 that is preceded by another extension header such as a Hop-by-Hop options header. Because ipv6_srh_rcv() restores skb->data by pushing a fixed sizeof(struct ipv6hdr) instead of re-establishing the real network header, skb_network_offset() remains negative; that negative value is then consumed as an unsigned length by the flow dissector during ip6_route_input(), or by sch_fragment()/neighbour output when the packet is forwarded via ip6_forward() or redirected via act_mirred, producing an out-of-bounds memcpy or buffer overflow that can crash the kernel and corrupt memory. Exploitation is not automatic: the target must be built with CONFIG_IPV6_SEG6 and configured as an SRv6 endpoint, and the packet must be specifically structured, which is reflected in the assessed vector AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H; no public exploit code and no confirmed active exploitation were identified at time of analysis. Vendor fixes are available in Linux 6.12.111, 6.18.53, 7.2.7 and 7.3-rc2.

RemediationAI

Apply the vendor patch by upgrading to Linux 6.12.111, 6.18.53, 7.2.7 or 7.3-rc2 (or any later release containing the backported commits ce4c8beedc19aceeab0e7bdc6f34394fb158c47c, 97b21ef57dfabbff660a4672c9fef7edfb720f47, 3ad7dca5e03bd64c65983a19734337512fd75491 and 975b5b067f525a1b1338c4a3bee1c46545801518), which normalise skb_network_offset() before routing/forwarding and restore skb->data to the SRH on the loopback path; these commits are the authoritative fix references. Where immediate kernel upgrade is not possible, the most effective compensating control is to eliminate the vulnerable code path entirely: rebuild the kernel without CONFIG_IPV6_SEG6, or, on modular builds, ensure the SRv6 handling is not reachable - the trade-off is that all IPv6 Segment Routing functionality is lost, which is not acceptable for telco/backbone and datacenter fabrics that rely on it. Second, if SRv6 must remain enabled, do not configure the host as an SRv6 endpoint or transit node that accepts SRH-bearing packets with segments_left > 0; restricting such traffic at the network edge (filtering IPv6 packets that combine a Hop-by-Hop options header with an SRH, and disabling act_mirred-based redirection of SRv6 traffic) blocks the forwarding and flow-dissection triggers, at the cost of reduced operational flexibility and possible breakage of legitimate SRv6 test/lab traffic. Disabling or tightly scoping SRv6-related forwarding offload and traffic mirroring reduces exposure to the sch_fragment()/neighbour-output branch but does not fix the routing-path flow-dissection issue. Note that separation of duties and monitoring should accompany these changes; the NVD record at https://nvd.nist.gov/vuln/detail/CVE-2026-98096 and the EUVD entry EUVD-2026-86926 can be used to track vendor advisory updates.

Affected VersionsENISA

Linux 4.10
Linux patch: 0
Linux patch: 7.2.7
Linux patch: 6.18.53
Linux patch: 7.3-rc2
Linux 1ababeba4a21f3dba3da3523c670b207fb2feb62 <975b5b067f525a1b1338c4a3bee1c46545801518
Linux 1ababeba4a21f3dba3da3523c670b207fb2feb62 <ce4c8beedc19aceeab0e7bdc6f34394fb158c47c
Linux patch: 6.12.111
Linux 1ababeba4a21f3dba3da3523c670b207fb2feb62 <97b21ef57dfabbff660a4672c9fef7edfb720f47
Linux 1ababeba4a21f3dba3da3523c670b207fb2feb62 <3ad7dca5e03bd64c65983a19734337512fd75491

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw class is an out-of-bounds memory access (negative skb_network_offset() interpreted as an unsigned length), though no CWE identifier was supplied with the advisory. The affected technology is IPv6 Segment Routing (SRv6), enabled at build time via CONFIG_IPV6_SEG6, in which a router/endpoint processes an SRH carried after the fixed IPv6 header. The kernel socket buffer tracks two positions: skb->data, the current parse cursor, and skb_network_header(), which points to the start of the IPv6 header. ipv6_srh_rcv() is entered with skb->data at the SRH; when segments_left > 0 it previously pushed sizeof(struct ipv6hdr) to reposition skb->data, silently assuming the SRH immediately follows the fixed header. If an extension header such as a Hop-by-Hop options header sits between the IPv6 header and the SRH, that assumption is wrong and skb_network_offset() (network header minus data) ends up negative. The negative offset is then mishandled in two downstream paths: fib6_rules_early_flow_dissect() calls __skb_flow_dissect() during ip6_route_input(), breaking C and BPF flow-dissector logic, and forwarding/redirection paths (ip6_forward(), act_mirred, sch_fragment(), neighbour output) treat the offset as a length, driving an out-of-bounds memcpy. The upstream fix pushes -skb_network_offset(skb) before routing so the offset is 0 for route lookup and forwarding, and on the loopback path pulls skb_transport_offset(skb) to restore skb->data to the SRH. The single CPE entry (cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:*) confirms the impact is kernel-wide for all releases carrying the vulnerable SRv6 code.

Know when Ipv6 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Linux) PRIMARY 7.4 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
vuln.today AI 6.5 MEDIUM

Remotely reachable crafted IPv6 SRH packet (AV:N/PR:N/UI:N) but requires SRv6 endpoint config and precise ext-header layout (AC:H); crash-dominant with some corruption, no leak (C:N/I:L/A:H).

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
SUSE 8.1 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

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

Lifecycle Timeline

4
CVSS changed
Sep 25, 2026 - 15:22 NVD
7.4 (HIGH)
Patch available
Sep 25, 2026 - 11:02 EUVD
CVE Published
Sep 25, 2026 - 10:24 cve.org
HIGH 7.4
CVE Published
Sep 25, 2026 - 10:24 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

ipv6: sr: restore network header before routing and forwarding

ipv6_srh_rcv() runs with skb->data at the Segment Routing Header (SRH) while skb_network_header() points at the IPv6 header.

When segments_left > 0, ipv6_srh_rcv() previously restored the skb->data position by pushing sizeof(struct ipv6hdr), assuming the SRH immediately followed the fixed IPv6 header. If another extension header (such as a Hop-by-Hop options header) precedes the SRH, skb_network_offset() remained negative.

This led to two problems:

  1. During ip6_route_input(), fib6_rules_early_flow_dissect() invokes

__skb_flow_dissect() which passes the negative skb_network_offset() to flow dissection, breaking BPF and C flow dissector logic.

  1. If forwarded via ip6_forward() or redirected via act_mirred, downstream

handlers (like sch_fragment() or neighbour output) pass the negative offset as an unsigned length, triggering OOB memcpy or buffer overflows.

Fix this by pushing -skb_network_offset(skb) before routing, ensuring skb_network_offset(skb) is 0 for route lookup / flow dissection as well as downstream forwarding. On the loopback path, pull skb_transport_offset(skb) to restore skb->data to the SRH before looping back.

Executive ViewAI

Why It Matters

Linux-based routers, edge appliances, and cloud network functions that terminate IPv6 Segment Routing (SRv6) traffic are exposed to a remotely reachable memory-corruption flaw in the kernel receive path (CVE-2026-98096, HIGH, CVSS 7.4) that can crash or destabilize the operating system. Exposure is limited to systems deliberately built with SRv6 support and configured as SRv6 endpoints, so the practical risk sits with network edge, telco, and cloud infrastructure teams rather than the general server estate. Because a vendor patch is already available and the failure mode is availability- and integrity-impacting, leadership should treat this as a targeted remediation item for the network-facing Linux fleet.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.4%
Top 63% exploitable
Prevalence
Low
Linux is ubiquitous but SRv6 segment-endpoint processing is a niche telco/datacenter feature
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
Medium

Priority Score

37
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +37
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy