{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98289 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98289 is a memory corruption vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98289 and fix it if it is affected.\n\nWhat it is: CVE-2026-98289 is a memory corruption vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98289 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-98289/ (Markdown: https://insights.sbomify.com/CVE-2026-98289/index.md)","id":"CVE-2026-98289","markdown":"https://insights.sbomify.com/CVE-2026-98289/index.md","name":"CVE-2026-98289","record":{"aliases":["AZL-106236","BELL-CVE-2026-98289","DEBIAN-CVE-2026-98289","GHSA-3rq9-mjhw-q3g6","UBUNTU-CVE-2026-98289"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A logic error in the Linux kernel's Unix socket garbage collector can cause memory leaks, leading to denial of service.","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\naf_unix: Unify scc_index when finalising SCC in __unix_walk_scc().\n\nCommit bfdb01283ee8 (\"af_unix: Assign a unique index to SCC.\")\nchanged Tarjan's algorithm to update lowlink with lowlink,\nwhich is called lowpoint (unix_vertex.scc_index).\n\nunix_vertex_dead() assumes all vertices in an SCC share the same\nlowpoint, but this is not always true if an SCC has two or more\nback edges, depending on the order of DFS.\n\nFor example, the graph below has two back edges from B to A\nand from C to B.\n\n  A --\u003e B --\u003e C\n  ^    | ^    |\n  `----' `----'\n\nIf DFS walks through A -\u003e B -\u003e C -\u003e B (-\u003e C -\u003e B) -\u003e A (-\u003e B -\u003e A),\neach index and scc_index will be updated as follows.\n\n  A --\u003e B --\u003e C    C = (3, 3)  (index, scc_index)\n                   B = (2, 2)\n                   A = (1, 1)\n\n  A ... B ... C    C = (3, 2)\u003c-.\n         ^    |    B = (2, 2) -'\n         `----'    A = (1, 1)\n\n  A ... B ... C    C = (3, 2)\n  ^    | .    .    B = (2, 1)\u003c-.\n  `----'  ....     A = (1, 1) -'\n\nThen, unix_vertex_dead() thinks that B is passed to another\nSCC with scc_index 2, and the SCC is not garbage-collected.\n\nThis does not happen if DFS walks in a different order below\nor starts from B.\n\n    1      3\n  A --\u003e B --\u003e C\n  ^    | ^    |\n  `----' `----'\n     2      4\n\nLet's unify scc_index across the SCC when finalising it.\n\nNote that updating v-\u003eindex was previously done in unix_scc_dead(),\nwhen called from __unix_walk_scc(), just to save one loop.  Since\n__unix_walk_scc() now iterates over the SCC anyway, the update is\nmoved back to __unix_walk_scc() and 'fast' argument is dropped.","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":"af_unix: Unify scc_index when finalising SCC in __unix_walk_scc().","id":"CVE-2026-98289","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup","id":"CVE-2026-98290"},"packages":[],"prev":{"headline":"net: stmmac: fix TSO header length truncation","id":"CVE-2026-98288"},"products":["Linux"],"published":"2026-10-06","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 logic error in the Linux kernel's Unix socket garbage collector can cause memory leaks, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-98289/"}