Answer in brief
CVE-2026-98950 records a Unknown severity vulnerability in flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 <c44c02c930c6583b235a1937c69ff716c4bb4514 || >=d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 <3fb5ad2951a6df92c98f4f06cd70f20c50a2eb2a || >=d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 <cc18eb0e9941162c03f03f411ed7f6c339d91fa0 || >=d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 <61b43a51a55929ec040bee3ea51af2121b956d05 || >=d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 <f202578efc738b883cfa04889eb97328914265a7 | c44c02c930c6583b235a1937c69ff716c4bb4514, 3fb5ad2951a6df92c98f4f06cd70f20c50a2eb2a, cc18eb0e9941162c03f03f411ed7f6c339d91fa0, 61b43a51a55929ec040bee3ea51af2121b956d05, f202578efc738b883cfa04889eb97328914265a7 |
| Linux/Linuxgeneric | 4.20 | Not reported |
Published upstream
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 23, 2026
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.
Quoted source text, attributed separately from HOL analysis.