{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98802 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98802 is a memory corruption vulnerability in Linux, published on 18 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98802 and fix it if it is affected.\n\nWhat it is: CVE-2026-98802 is a memory corruption vulnerability in Linux, published on 18 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98802 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-98802/ (Markdown: https://insights.sbomify.com/CVE-2026-98802/index.md)","id":"CVE-2026-98802","markdown":"https://insights.sbomify.com/CVE-2026-98802/index.md","name":"CVE-2026-98802","record":{"aliases":["AZL-109146","BELL-CVE-2026-98802","DEBIAN-CVE-2026-98802","GHSA-mq8p-h4gv-vq5x","UBUNTU-CVE-2026-98802"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"An attacker can read or modify shared packet data in the Linux kernel via Segment Routing, potentially leaking information or corrupting network traffic.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","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\nseg6: ensure packet data is writable before modifying SRH and IPv6 DA\n\nadvance_nextseg() modifies the SRH Segments Left field and the IPv6\ndestination address without ensuring the packet data is writable.\nseg6_next_csid_advance_arg() has the same problem when it advances the\nNEXT-C-SID argument in the destination address.\n\nThe skb may be cloned, for example by an AF_PACKET socket receiving on\nthe ingress device. advance_nextseg() and seg6_next_csid_advance_arg()\nthen write into the packet data shared with the clone. A read from that\nsocket can return the modified packet instead of the received one. The\nsimplified path below shows this for advance_nextseg():\n\n__netif_receive_skb_one_core\n  __netif_receive_skb_core\n    deliver_skb               [orig: users=2, cloned=0]\n      packet_rcv\n        skb_clone             clone queued to the AF_PACKET socket\n        consume_skb(orig)     [orig: users=1, cloned=1]\n  ipv6_rcv\n    ip6_rcv_core              skb_share_check: no-op [orig: users=1]\n    [...]\n      input_action_end_core\n        advance_nextseg       writes into the data shared with the clone\n\nCall skb_ensure_writable() in advance_nextseg() and in\nseg6_next_csid_advance_arg() before they modify the packet data.\nskb_ensure_writable() may reallocate skb-\u003ehead, which invalidates the\npointers into the packet data taken before the call.\nadvance_nextseg() now returns a valid SRH pointer, or NULL if\nskb_ensure_writable() fails.\nseg6_next_csid_advance_arg() takes the pointer to the destination\naddress from the skb after skb_ensure_writable().\nOn failure, the callers drop the packet with SKB_DROP_REASON_NOMEM.","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":"seg6: ensure packet data is writable before modifying SRH and IPv6 DA","id":"CVE-2026-98802","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"net: stmmac: fix rx Scatter-Gather support","id":"CVE-2026-98803"},"packages":[],"prev":{"headline":"net: restrict SO_RESERVE_MEM to TCP sockets and cap max value","id":"CVE-2026-98801"},"products":["Linux"],"published":"2026-10-18","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-19","vendors":["Linux"]},"summary":"An attacker can read or modify shared packet data in the Linux kernel via Segment Routing, potentially leaking information or corrupting network traffic.","url":"https://insights.sbomify.com/CVE-2026-98802/"}