{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97596 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97596 is a memory corruption vulnerability in Linux, published on 25 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-97596 and fix it if it is affected.\n\nWhat it is: CVE-2026-97596 is a memory corruption vulnerability in Linux, published on 25 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-97596 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-97596/ (Markdown: https://insights.sbomify.com/CVE-2026-97596/index.md)","id":"CVE-2026-97596","markdown":"https://insights.sbomify.com/CVE-2026-97596/index.md","name":"CVE-2026-97596","record":{"aliases":["AZL-104652","BELL-CVE-2026-97596","DEBIAN-CVE-2026-97596","GHSA-x8xm-jq59-9m58","UBUNTU-CVE-2026-97596"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel IPVS","requires_auth":"none","summary":"An attacker can send crafted IPVS sync records to trigger out-of-bounds memory access, potentially leading to code execution or system crash.","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\nipvs: reject invalid states in connection template sync records\n\nIPVS sync receivers validate protocol states before creating or updating a\nconnection. For connection templates, however, they only log states outside\nthe template state range and still store the value in the connection.\n\nA template can be returned by ordinary connection lookup. TCP and SCTP then\nuse the invalid state as an index into their transition tables.\n\nReject invalid template states in both sync protocol versions before\nlooking up or modifying a connection. The version 1 path handles both\nIPv4 and IPv6 records.","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: reject invalid states in connection template sync records","id":"CVE-2026-97596","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":"ipv6: flowlabel: cap duplicate leases per socket","id":"CVE-2026-97597"},"packages":[],"prev":{"headline":"mac802154: fix use-after-free of sdata via queued RX frames","id":"CVE-2026-97595"},"products":["Linux"],"published":"2026-09-25","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":"An attacker can send crafted IPVS sync records to trigger out-of-bounds memory access, potentially leading to code execution or system crash.","url":"https://insights.sbomify.com/CVE-2026-97596/"}