CVE-2026-80905
Description
A flaw was found in the kernel. When processing VLAN-tagged frames, the network header is incorrectly advanced past the VLAN tag before the transport header is probed. This misinterprets the inner protocol header as a VLAN header, resulting in an uninitialized transport header. This issue can lead to incorrect packet dissection and potentially affect network functionality.
Statement
A VLAN tagged frame sent through the TAP transmit path can leave skb transport_header unset because skb_probe_transport_header is called after network_header has already been advanced past the VLAN header. The flow dissector then interprets the inner protocol header as a VLAN header, fails to identify the real transport offset, and the skb may continue through dev_queue_xmit with a sentinel transport_header value. For the CVSS the PR:N is used in the paranoid interpretation because a malicious guest or adjacent virtual network peer may be able to provide VLAN tagged frames to an already configured TAP path without host administrative privileges. The issue is not directly Internet reachable in normal deployments because TAP is a local or virtual network device path. Impact is most likely denial of service or incorrect packet metadata handling, with limited integrity impact possible if later packet processing depends on the wrong transport header.
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 | 6.2 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | 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 | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory)
An attacker could provide unexpected values and cause a program crash or arbitrary control of resource allocation, leading to excessive consumption of resources such as memory and CPU.
Confidentiality
Technical Impact: Read Memory; Read Files or Directories
An attacker could read confidential data if they are able to control resource references.
Integrity,Confidentiality,Availability
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
An attacker could use malicious input to modify data or possibly alter control flow in unexpected ways, including arbitrary command execution.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.