CVE-2026-98306
Description
A flaw was found in the Linux kernel's IPv6 Segment Routing (SRv6) subsystem. When decapsulating IPv4 network traffic on an interface bound to a Virtual Routing and Forwarding (VRF) domain—a feature used to isolate network traffic—the kernel fails to properly preserve routing domain flags. A remote attacker could exploit this vulnerability by sending SRv6 packets to an affected system. This flaw allows decapsulated network traffic to bypass VRF isolation boundaries and be delivered to unintended listening sockets outside the isolated domain, potentially resulting in unauthorized data exposure.
Statement
An SRv6 End.DX4 decapsulation path can lose the L3 slave marker when converting the outer IPv6 control block into the inner IPv4 control block. The decapsulated packet can therefore be processed as if it belonged to the default VRF, allowing an unbound socket outside the ingress VRF to receive traffic that should remain scoped to the enslaved interface. This creates a potential VRF isolation bypass with limited confidentiality and integrity impact, while the intended VRF bound socket may not receive the packet. For the CVSS the PR:N value is selected because a remote sender does not need an account or privileges on the target when the configured SRv6 endpoint is reachable. Exploitation requires a system using SRv6 End.DX4 with a VRF enslaved ingress interface and a packet addressed so that processing reaches local socket lookup. The issue is network reachable, although practical exposure is generally limited to routed SRv6 infrastructure or controlled service provider and data center networks. There is no memory corruption primitive or evidence of privilege escalation.
Mitigation
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7 | N/A | N/A |
| Attack Vector | Network | N/A | N/A |
| Attack Complexity | High | N/A | N/A |
| Privileges Required | None | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | Low | N/A | N/A |
| Integrity Impact | Low | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H
Understanding the Weakness (CWE)
Other
Technical Impact: Varies by Context; Gain Privileges or Assume Identity
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.