{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98955 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-98955 is a vulnerability in Linux, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-98955 and fix it if it is affected.\n\nWhat it is: CVE-2026-98955 is a vulnerability in Linux, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-98955 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98955/ (Markdown: https://insights.sbomify.com/CVE-2026-98955/index.md)","id":"CVE-2026-98955","markdown":"https://insights.sbomify.com/CVE-2026-98955/index.md","name":"CVE-2026-98955","record":{"aliases":["AZL-110765","BELL-CVE-2026-98955","DEBIAN-CVE-2026-98955","GHSA-935w-9g6m-g833","UBUNTU-CVE-2026-98955"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nflow_dissector: avoid u16 truncation of skb-\u003elen when computing thoff\n\n__skb_flow_dissect() computes key_control-\u003ethoff using:\n\n  key_control-\u003ethoff = min_t(u16, nhoff, skb ? skb-\u003elen : hlen);\n\nmin_t(u16, ...) casts both arguments to u16 before comparing them.\nWhenever skb-\u003elen (or hlen) modulo 65536 is smaller than nhoff, the\ntruncated length wins and thoff is set to a bogus small value, even\nwhen the dissection succeeded. For example, an IPv4/TCP frame with\nskb-\u003elen == 65540 and nhoff == 34 gets thoff == 4, so callers such as\nskb_probe_transport_header() point the transport header inside the\nEthernet header.\n\nSuch skbs are not exotic:\n- At the time of commit d0c081b49137 (\"flow_dissector: properly cap\n  thoff field\"), AF_PACKET with PACKET_VNET_HDR could already build GSO\n  skbs larger than 64KB (MTU checks are skipped for GSO, and\n  alloc_skb_with_frags() accepted up to MAX_SKB_FRAGS (17) order-0\n  pages on top of the linear part).\n- BIG TCP now makes skbs larger than 64KB common.\n- The following patch makes tun_get_user() dissect IFF_TAP frames\n  before eth_type_trans() pulls the Ethernet header, so a GSO frame\n  carrying a 65522..65535 byte L3 packet will be dissected with\n  skb-\u003elen in [65536, 65549].\n\nCompare as u32 instead. If the resulting offset cannot be represented\nin the u16 key_control-\u003ethoff, cap it to U16_MAX and report the\ndissection as failed rather than silently returning a wrong transport\noffset. thoff is still set on failure, as some callers (such as\neth_get_headlen()) use it regardless of the return value.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"flow_dissector: avoid u16 truncation of skb-\u003elen when computing thoff","id":"CVE-2026-98955","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"ASoC: adau1372: allow sleepy powerdown GPIOs","id":"CVE-2026-98956"},"packages":[],"prev":{"headline":"net: always dissect GSO packets in __virtio_net_hdr_to_skb()","id":"CVE-2026-98954"},"products":["Linux"],"published":"2026-10-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-23","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-98955/"}