{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72418 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72418 is a high-severity denial of service vulnerability in Linux, published on 15 Aug 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-72418 and fix it if it is affected.\n\nWhat it is: CVE-2026-72418 is a high-severity denial of service vulnerability in Linux, published on 15 Aug 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-72418 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-72418/ (Markdown: https://insights.sbomify.com/CVE-2026-72418/index.md)","id":"CVE-2026-72418","markdown":"https://insights.sbomify.com/CVE-2026-72418/index.md","name":"CVE-2026-72418","record":{"aliases":["BELL-CVE-2026-72418","DEBIAN-CVE-2026-72418","GHSA-prxp-6xjx-9qx5","UBUNTU-CVE-2026-72418"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Linux kernel netfilter","requires_auth":"none","summary":"A regression in Linux kernel netfilter connlimit causes valid connections to be dropped, leading to denial of service for network services.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_conncount: prevent connlimit drops for early confirmed ct\n\nCommit 69894e5b4c5e (\"netfilter: nft_connlimit: update the count if add\nwas skipped\") introduced a regression where packets for valid\nconnections are dropped when using connlimit for soft-limiting\nscenarios.\n\nThe issue occurs when a new connection reuses a socket currently in\nthe TIME_WAIT state. In this scenario, the connection tracking entry\nis evaluated as already confirmed. Previously, __nf_conncount_add()\nassumed that if a connection was confirmed and did not originate from\nthe loopback interface, it should skip the addition and return -EEXIST.\n\nSkipping the addition triggers a garbage collection run that cleans up\nthe TIME_WAIT connection. Consequently, the active connection count\ndrops to 0, which xt_connlimit mishandles, leading to the false rejection\nof the perfectly valid new connection.\n\nFix this by replacing the interface check with protocol-agnostic state\nchecks. We now skip the tree insertion and preserve the lockless garbage\ncollection optimization only if the connection is IPS_ASSURED. This\nallows early-confirmed setup packets (such as reused TIME_WAIT sockets\nor locally generated SYN-ACKs) to be properly evaluated and counted\nwithout falsely dropping. The goto check_connections path is maintained\nto ensure these setup packets are deduplicated correctly.\n\nThis has been tested with slowhttptest and HTTP server configured\nlocally to ensure we are not breaking soft-limiting scenarios for local\nor external connections. In addition, it was tested with a OVS zone\nlimit too.","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":"netfilter: nf_conncount: prevent connlimit drops for early confirmed ct","id":"CVE-2026-72418","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"netfilter: nf_nat: avoid invalid nat_net pointer use on failed nf_nat_init()","id":"CVE-2026-72419"},"packages":[],"prev":{"headline":"netfilter: flowtable: Validate iph-\u003eihl in nf_flow_ip4_tunnel_proto()","id":"CVE-2026-72417"},"products":["Linux"],"published":"2026-08-15","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Linux"]},"summary":"A regression in Linux kernel netfilter connlimit causes valid connections to be dropped, leading to denial of service for network services.","url":"https://insights.sbomify.com/CVE-2026-72418/"}