{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72429 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72429 is a critical memory corruption 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-72429 and fix it if it is affected.\n\nWhat it is: CVE-2026-72429 is a critical memory corruption 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-72429 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-72429/ (Markdown: https://insights.sbomify.com/CVE-2026-72429/index.md)","id":"CVE-2026-72429","markdown":"https://insights.sbomify.com/CVE-2026-72429/index.md","name":"CVE-2026-72429","record":{"aliases":["BELL-CVE-2026-72429","DEBIAN-CVE-2026-72429","GHSA-34fv-pgg7-6wvm","UBUNTU-CVE-2026-72429"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Linux kernel","requires_auth":"none","summary":"A type confusion vulnerability in the Linux kernel IPv6 IOAM module allows invalid pointer access, potentially leading to code execution or denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/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\nipv6: ioam: fix type confusion of dst_entry\n\nIOAM uses a dummy dst_entry(null_dst) to mark that the destination should\nnot be changed after the transformation. This dst is stored in the IOAM lwt\nstate and may be passed to dst_cache_set_ip6().\n\nHowever, the IPv6 dst cache path eventually calls rt6_get_cookie(), which\ntreats the dst_entry as part of a struct rt6_info. Since the null_dst was\nembedded directly as a struct dst_entry in struct ioam6_lwt, this resulted\nin an invalid cast and rt6_get_cookie() reading fields from the wrong\nobject.\n\nIn practice, the wrong cookie is not used while dst-\u003eobsolete is zero, but\nrt6_get_cookie() may also access per-cpu value when rt-\u003esernum is\nzero. In this case, rt-\u003esernum aliases ioam6_lwt::cache::reset_ts, which\ncan become zero, making this a potential invalid pointer access.\n\nFix this by embedding a full struct rt6_info for the dummy IPv6 route and\npassing its dst member to the dst APIs.","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: ioam: fix type confusion of dst_entry","id":"CVE-2026-72429","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":"net/sched: act_ct: fix nf_connlabels leak on two error paths","id":"CVE-2026-72430"},"packages":[],"prev":{"headline":"bpf: Fix stack slot index in nospec checks","id":"CVE-2026-72428"},"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A type confusion vulnerability in the Linux kernel IPv6 IOAM module allows invalid pointer access, potentially leading to code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2026-72429/"}