{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98598 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98598 is a denial of service 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-98598 and fix it if it is affected.\n\nWhat it is: CVE-2026-98598 is a denial of service 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-98598 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-98598/ (Markdown: https://insights.sbomify.com/CVE-2026-98598/index.md)","id":"CVE-2026-98598","markdown":"https://insights.sbomify.com/CVE-2026-98598/index.md","name":"CVE-2026-98598","record":{"aliases":["AZL-108809","BELL-CVE-2026-98598","DEBIAN-CVE-2026-98598","GHSA-3wx3-9xwg-38ff","UBUNTU-CVE-2026-98598"],"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":"A race condition in the Linux kernel IPv6 stack allows attackers to cause a denial of service by stalling network device unregistration through reference leaks.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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\nipv6: Prevent rt6_insert_exception() for dying fib6_info.\n\nBefore the cited commit, fib6_nh_flush_exceptions() always set\nfrom-\u003eexception_bucket_flushed = 1 under rt6_exception_lock to\nprevent rt6_insert_exception() from inserting a new exception\nfor a dying fib6_info.\n\nThe flag was replaced with the FIB6_EXCEPTION_BUCKET_FLUSHED\nbit stored in nh-\u003ert6i_exception_bucket.\n\nThe problem is that now the bit is only set when the bucket\nis not NULL and fib6_nh_flush_exceptions() is called from\nfib6_nh_release() after fib6_ref has already reached zero.\n\nIf rt6_insert_exception() is called while the target fib6_info\nis being removed via fib6_purge_rt(), a new exception could be\ncreated successfully because rt6_flush_exceptions() no longer\nsets the bit.\n\nThis creates a reference cycle between the fib6_info and the\nexception route, leaking the fib6_info, its nexthop device,\nand all per-CPU routes in fib6_nh-\u003ert6i_pcpu, which stalls netdev\nunregistration.\n\n[   34.680602] unregister_netdevice: waiting for gre6 to become free. Usage count = 68\n[   44.920675] unregister_netdevice: waiting for gre6 to become free. Usage count = 68\n[   55.176582] unregister_netdevice: waiting for gre6 to become free. Usage count = 68\n\nLet's call fib6_drop_pcpu_from() before rt6_flush_exceptions(),\nto set fib6_destroying before rt6_exception_lock, and check\nf6i-\u003efib6_destroying in rt6_insert_exception().\n\nNote that FIB6_EXCEPTION_BUCKET_FLUSHED logic is dead and\nwe can clean it up in net-next.","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":"ipv6: Prevent rt6_insert_exception() for dying fib6_info.","id":"CVE-2026-98598","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"bpf: Reject non-negative offsets in stack_slot_obj_get_spi()","id":"CVE-2026-98599"},"packages":[],"prev":{"headline":"net: usb: sr9700: include receive overhead in the length check","id":"CVE-2026-98597"},"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 race condition in the Linux kernel IPv6 stack allows attackers to cause a denial of service by stalling network device unregistration through reference leaks.","url":"https://insights.sbomify.com/CVE-2026-98598/"}