Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98950

flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect()

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 28 days later

    Published

  3. · 7 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 – < 46d21495f633e38d40857401504ee51c56ffed2a
    • affected d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 – < 6267f8304cbd9ec9f3f53bd227a733e07131492e
    • affected d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 – < 99c59062172620a0bac4ae8cf37c83bb78772cdd
    • affected d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 – < c44c02c930c6583b235a1937c69ff716c4bb4514
    • affected d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 – < 3fb5ad2951a6df92c98f4f06cd70f20c50a2eb2a
    • affected d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 – < cc18eb0e9941162c03f03f411ed7f6c339d91fa0
    • affected d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 – < 61b43a51a55929ec040bee3ea51af2121b956d05
    • affected d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 – < f202578efc738b883cfa04889eb97328914265a7
  • Linux · Linux

    • affected 4.20
    • unaffected < 4.20
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.11 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98950 badge
[![CVE-2026-98950](https://cveledger.app/badge/CVE-2026-98950.svg)](https://cveledger.app/cve/CVE-2026-98950)

Record last updated .