CVE-2026-98950 json
flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect()
published 19d ago modified 12d ago also EUVD-2026-108924
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect()
bpf_flow_dissect() sanitizes the offsets returned by the BPF program with clamp_t(u16, ..., hlen).
If hlen is bigger than 65535, the upper bound is truncated before the comparison. For instance, with hlen == 65536, both nhoff and thoff are forced to zero, even if the program returned sane values.
This is the same class of bug as the one fixed in commit 99bda1ecbd56 ("flow_dissector: avoid u16 truncation of skb->len when computing thoff"). That fix does not cover the BPF path, because __skb_flow_dissect() returns early when a BPF flow dissector handles the packet.
struct bpf_flow_keys stores nhoff and thoff as u16, so cap hlen to U16_MAX before clamping.
Found by sashiko while reviewing the commit above.
Patch / fix
- Linux Linux 7.3
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.11-1
debian advisories DEBIAN-CVE-2026-98950
- linux Ubuntu 26.10 7.3.0-10.10
- linux-aws Ubuntu 26.10 7.3.0-1004.4
- linux-gcp Ubuntu 26.10 7.3.0-1004.4
- linux-raspi Ubuntu 26.10 7.3.0-1004.4
- linux-riscv Ubuntu 26.10 7.3.0-10.10.1
- linux-oracle Ubuntu 26.10 7.3.0-1004.4
- linux-realtime Ubuntu 26.10 7.3.0-10.10.1
ubuntu advisories UBUNTU-CVE-2026-98950
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-110756
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/46d21495f633e38d40857401504ee51c56ffed2a commit
- git.kernel.org/stable/c/6267f8304cbd9ec9f3f53bd227a733e07131492e commit
- git.kernel.org/stable/c/99c59062172620a0bac4ae8cf37c83bb78772cdd commit
- git.kernel.org/stable/c/c44c02c930c6583b235a1937c69ff716c4bb4514 commit
- git.kernel.org/stable/c/3fb5ad2951a6df92c98f4f06cd70f20c50a2eb2a commit
- git.kernel.org/stable/c/cc18eb0e9941162c03f03f411ed7f6c339d91fa0 commit
- git.kernel.org/stable/c/61b43a51a55929ec040bee3ea51af2121b956d05 commit
- git.kernel.org/stable/c/f202578efc738b883cfa04889eb97328914265a7 commit
Is CVE-2026-98950 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-98950 updated cvss 3.7
kernel: flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/46d21495f633e38d40857401504ee51c56ffed2a
- git.kernel.org /stable/c/6267f8304cbd9ec9f3f53bd227a733e07131492e
- git.kernel.org /stable/c/99c59062172620a0bac4ae8cf37c83bb78772cdd
- git.kernel.org /stable/c/c44c02c930c6583b235a1937c69ff716c4bb4514
- git.kernel.org /stable/c/3fb5ad2951a6df92c98f4f06cd70f20c50a2eb2a
- git.kernel.org /stable/c/cc18eb0e9941162c03f03f411ed7f6c339d91fa0
- git.kernel.org /stable/c/61b43a51a55929ec040bee3ea51af2121b956d05
- git.kernel.org /stable/c/f202578efc738b883cfa04889eb97328914265a7
Sources
- CVE List CVE-2026-98950
- NVD CVE-2026-98950
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.