Vulnerability · Published Oct 23, 2026 · Assigned by Linux

CVE-2026-98955flow_dissector: avoid u16 truncation of skb->len when computing thoff

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 11% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 88.6% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: flow_dissector: avoid u16 truncation of skb->len when computing thoff __skb_flow_dissect() computes key_control->thoff using: key_control->thoff = min_t(u16, nhoff, skb ? skb->len : hlen); min_t(u16, ...) casts both arguments to u16 before comparing them. Whenever skb->len (or hlen) modulo 65536 is smaller than nhoff, the truncated length wins and thoff is set to a bogus small value, even when the dissection succeeded. For example, an IPv4/TCP frame with skb->len == 65540 and nhoff == 34 gets thoff == 4, so callers such as skb_probe_transport_header() point the transport header inside the Ethernet header. Such skbs are not exotic: - At the time of commit d0c081b49137 ("flow_dissector: properly cap thoff field"), AF_PACKET with PACKET_VNET_HDR could already build GSO skbs larger than 64KB (MTU checks are skipped for GSO, and alloc_skb_with_frags() accepted up to MAX_SKB_FRAGS (17) order-0 pages on top of the linear part). - BIG TCP now makes skbs larger than 64KB common. - The following patch makes tun_get_user() dissect IFF_TAP frames before eth_type_trans() pulls the Ethernet header, so a GSO frame carrying a 65522..65535 byte L3 packet will be dissected with skb->len in [65536, 65549]. Compare as u32 instead. If the resulting offset cannot be represented in the u16 key_control->thoff, cap it to U16_MAX and report the dissection as failed rather than silently returning a wrong transport offset. thoff is still set on failure, as some callers (such as eth_get_headlen()) use it regardless of the return value.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-98955
Debian:13linux6.12.113-1DEBIAN-CVE-2026-98955
Debian:14linux7.2.11-1DEBIAN-CVE-2026-98955
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.04:LTSlinuxno fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.10linux7.3.0-10.10UBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.10linux-aws7.3.0-1004.4UBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.10linux-azureno fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.10linux-gcp7.3.0-1004.4UBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-hwe-7.0no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.04:LTSlinux-oem-7.0no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.10linux-oracle7.3.0-1004.4UBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.10linux-raspi7.3.0-1004.4UBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.10linux-realtime7.3.0-10.10.1UBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-98955
Ubuntu:26.10linux-riscv7.3.0-10.10.1UBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-riscv-7.0no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-98955
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-98955
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-98955

Affected products (as reported)

VendorProductVersions
Linux Linux d0c081b49137cd3200f2023c0875723be66e7ce5 – before 3f6000fdf8a57b9786669869af8a3e050b541bf3d0c081b49137cd3200f2023c0875723be66e7ce5 – before 2c2f82b696c5e877f60ea77b7784e906a5e63014d0c081b49137cd3200f2023c0875723be66e7ce5 – before d44e66f5dd99319a32e378b610af7fcf78da985ad0c081b49137cd3200f2023c0875723be66e7ce5 – before d9e08836d06c84abb18470c94b12b131eaccdc7dd0c081b49137cd3200f2023c0875723be66e7ce5 – before 50d0cd575cab763f833d6ac6eb6550b23a0b3daed0c081b49137cd3200f2023c0875723be66e7ce5 – before 9993e6a0ac1b5b3101ffba702cacb9f42b9909d8d0c081b49137cd3200f2023c0875723be66e7ce5 – before 52efce4755a4b8b82039caa773645ffc80b25362d0c081b49137cd3200f2023c0875723be66e7ce5 – before 99bda1ecbd56905f8bd934b9cdccd3bd251192b1
Linux Linux 4.15

References