{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74670 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74670 is a high-severity vulnerability in Linux, published on 22 Aug 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-74670 and fix it if it is affected.\n\nWhat it is: CVE-2026-74670 is a high-severity vulnerability in Linux, published on 22 Aug 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-74670 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-74670/ (Markdown: https://insights.sbomify.com/CVE-2026-74670/index.md)","id":"CVE-2026-74670","markdown":"https://insights.sbomify.com/CVE-2026-74670/index.md","name":"CVE-2026-74670","record":{"aliases":["AZL-97365","BELL-CVE-2026-74670","DEBIAN-CVE-2026-74670","GHSA-98mw-8627-45gg","UBUNTU-CVE-2026-74670"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel IPVS","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel IPVS estimator allows out-of-bounds writes during namespace teardown, potentially causing a denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/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\nipvs: stop estimator after disabled calc phase\n\nIPVS estimator kthread 0 starts with zeroed chain and tick limits until\nits initial calculation phase completes. If network namespace teardown\nclears ipvs-\u003eenable during that phase, ip_vs_est_calc_phase() can return\nwithout installing positive limits.\n\nThe kthread can then continue into its main loop and drain\nest_temp_list with zero chain_max, tick_max and est_max_count values.\nEach enqueue consumes one available tick row, but est_count never\nreaches the zero est_max_count value. After all rows are consumed, the\nrow lookup returns IPVS_EST_NTICKS and ip_vs_enqueue_estimator() writes\npast the ticks and tick_len arrays.\n\nExit kthread 0 after the calculation phase if the kthread is stopping or\nIPVS has been disabled. That keeps temporary estimators from being\ndrained after the limits failed to initialize.\n\nEstimator kthreads can now self-exit before teardown or reload stops\nkd-\u003etask. Keep an extra task reference after creation and release it\nwith kthread_stop_put(), so kd-\u003etask remains valid until the stop paths\nconsume that reference.","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":"ipvs: stop estimator after disabled calc phase","id":"CVE-2026-74670","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"ima: fix out-of-bounds read in xattr_verify()","id":"CVE-2026-74671"},"packages":[],"prev":{"headline":"ipvs: clear IPv4 options after rebasing tunnel ICMP errors","id":"CVE-2026-74669"},"products":["Linux"],"published":"2026-08-22","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-08-25","vendors":["Linux"]},"summary":"A race condition in the Linux kernel IPVS estimator allows out-of-bounds writes during namespace teardown, potentially causing a denial of service.","url":"https://insights.sbomify.com/CVE-2026-74670/"}