{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98570 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98570 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-98570 and fix it if it is affected.\n\nWhat it is: CVE-2026-98570 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-98570 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-98570/ (Markdown: https://insights.sbomify.com/CVE-2026-98570/index.md)","id":"CVE-2026-98570","markdown":"https://insights.sbomify.com/CVE-2026-98570/index.md","name":"CVE-2026-98570","record":{"aliases":["AZL-109086","BELL-CVE-2026-98570","DEBIAN-CVE-2026-98570","GHSA-4prh-wfp5-28j7","UBUNTU-CVE-2026-98570"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Linux kernel","requires_auth":"none","summary":"A memory corruption vulnerability in the Linux kernel IPv6 stack allows remote attackers to cause denial of service or execute code via crafted 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\nnet: ipv6: keep room for the mac header in dst_dev_overhead()\n\nThe seg6, ioam6 and rpl lwtunnels size their skb_cow_head() request as\nthe length they are about to push plus dst_dev_overhead(), then push the\nnew headers and rebuild the mac header below them with\nskb_mac_header_rebuild().  That rebuild needs skb-\u003emac_len of headroom,\nbut dst_dev_overhead() leaves LL_RESERVED_SPACE() of the egress device,\n16 bytes for plain Ethernet.\n\nWhere the mac header is longer than that, as it is on ingress through a\nVLAN device with reorder_hdr off, the rebuild runs out of room:\nskb_set_mac_header(skb, -skb-\u003emac_len) computes a negative offset,\nstores it unchecked in the u16 skb-\u003emac_header, and the memmove that\nfollows writes skb-\u003emac_len bytes about 64 KB past skb-\u003ehead.\nForwarding plain ping6 traffic through such a device reproduces it on\nall five seg6 encapsulation modes and on the rpl and ioam6 inline paths;\nskb-\u003emac_header comes back as 65534 on a 704-byte head.\n\nReturn the larger of the two.  The helper already returns skb-\u003emac_len\nwhen it has no dst, so this only makes the other branch agree, and it\ncovers every caller rather than each call site in turn.","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":"net: ipv6: keep room for the mac header in dst_dev_overhead()","id":"CVE-2026-98570","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: clear stale buf-\u003epage after recycling on skb build failure","id":"CVE-2026-98571"},"packages":[],"prev":{"headline":"ip_gre: Reject enabling collect metadata through changelink","id":"CVE-2026-98569"},"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":"A memory corruption vulnerability in the Linux kernel IPv6 stack allows remote attackers to cause denial of service or execute code via crafted network traffic.","url":"https://insights.sbomify.com/CVE-2026-98570/"}