{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89783 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89783 is a critical memory corruption vulnerability in Linux, published on 16 Sep 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-89783 and fix it if it is affected.\n\nWhat it is: CVE-2026-89783 is a critical memory corruption vulnerability in Linux, published on 16 Sep 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-89783 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-89783/ (Markdown: https://insights.sbomify.com/CVE-2026-89783/index.md)","id":"CVE-2026-89783","markdown":"https://insights.sbomify.com/CVE-2026-89783/index.md","name":"CVE-2026-89783","record":{"aliases":["AZL-101337","BELL-CVE-2026-89783","DEBIAN-CVE-2026-89783","GHSA-w5hj-mmmx-p42j","UBUNTU-CVE-2026-89783"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"An off-by-one error in the Linux kernel IPv6 XFRM input path allows an out-of-bounds write, potentially causing a kernel panic and denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nxfrm6: fix out-of-bounds write in xfrm6_input_addr() when secpath is full\n\nThe depth check in xfrm6_input_addr() is off by one:\n\n  if (1 + sp-\u003elen == XFRM_MAX_DEPTH)\n          goto drop;\n  ...\n  sp-\u003exvec[sp-\u003elen++] = x;\n\nxfrm_input() can leave sp-\u003elen == XFRM_MAX_DEPTH, and the transport-mode\nreceive path re-enters IPv6 input via xfrm_trans_reinject() with that\nsecpath preserved. If the inner packet carries a destination-options HAO\noption or a type-2 routing header, xfrm6_input_addr() is called with\nsp-\u003elen == XFRM_MAX_DEPTH; the check (1 + 6 == 6) is false, so\nsp-\u003exvec[sp-\u003elen++] writes one slot past the 6-element xvec[]. The write\nstays within the sec_path allocation (invisible to KASAN); UBSAN_BOUNDS\nflags it and panics under panic_on_warn.\n\nUse \"sp-\u003elen \u003e= XFRM_MAX_DEPTH\", matching xfrm_input(). This also\nrestores one chain level the old check rejected at sp-\u003elen == 5.\n\n  UBSAN: array-index-out-of-bounds in net/ipv6/xfrm6_input.c:309:10\n  index 6 is out of range for type 'xfrm_state *[6]'","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":"xfrm6: fix out-of-bounds write in xfrm6_input_addr() when secpath is full","id":"CVE-2026-89783","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"SUNRPC: check rpc_sockaddr2uaddr() return value in rpcb_register_inet4/6","id":"CVE-2026-89784"},"packages":[],"prev":{"headline":"fs/ntfs3: reject restart table growth beyond U16_MAX entries","id":"CVE-2026-89782"},"products":["Linux"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"An off-by-one error in the Linux kernel IPv6 XFRM input path allows an out-of-bounds write, potentially causing a kernel panic and denial of service.","url":"https://insights.sbomify.com/CVE-2026-89783/"}