{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68415 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68415 is a high-severity use after free vulnerability in Linux, published on 10 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-68415 and fix it if it is affected.\n\nWhat it is: CVE-2026-68415 is a high-severity use after free vulnerability in Linux, published on 10 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-68415 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-68415/ (Markdown: https://insights.sbomify.com/CVE-2026-68415/index.md)","id":"CVE-2026-68415","markdown":"https://insights.sbomify.com/CVE-2026-68415/index.md","name":"CVE-2026-68415","record":{"aliases":["BELL-CVE-2026-68415","DEBIAN-CVE-2026-68415","GHSA-f6q7-mj5x-h2px","UBUNTU-CVE-2026-68415"],"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":"low_privilege","summary":"A use-after-free in the Linux kernel xfrm subsystem allows a local attacker to cause a system crash via a kernel panic.","user_interaction":"not_required","vuln_class":"use_after_free"},"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\nxfrm: clear mode callbacks after failed mode setup\n\nxfrm_state_gc_task can run long after a failed IPTFS state setup. In the\nreproduced case, __xfrm_init_state() cached x-\u003emode_cbs, IPTFS setup\nreturned -ENOMEM before publishing mode_data, and the temporary module\nreference from xfrm_get_mode_cbs() was dropped immediately. The dead state\nthen kept x-\u003emode_cbs until deferred GC ran after xfrm_iptfs had been\nunloaded.\n\nClear x-\u003emode_cbs when mode init or clone fails before publishing\nmode_data. Those states never installed mode-specific state or the\nlong-term IPTFS module pin, so deferred GC has nothing mode-specific to\ndestroy and must not retain a callback table pointer past the temporary\nlookup reference.\n\nThe buggy scenario involves two paths, with each column showing the order\nwithin that path:\n\nfailed setup path:\n1. cache x-\u003emode_cbs\n2. mode setup fails before mode_data\n3. drop the temporary module ref\n4. dead state keeps x-\u003emode_cbs cached\n\nGC/unload path:\n1. xfrm_state_put() queues GC work\n2. xfrm_iptfs unloads later\n3. xfrm_state_gc_task runs\n4. GC dereferences stale x-\u003emode_cbs\n\nThis also covers the failed clone path where clone_state() returns before\npublishing mode_data.\n\nValidation reproduced this kernel report:\nKernel panic - not syncing: Fatal exception\nCONFIG_FAULT_INJECTION_STACKTRACE_FILTER=y\nfailslab_stacktrace_filter matched xfrm_iptfs frames\nack_error=-12\nFAULT_INJECTION: forcing a failure\nBUG: unable to handle page fault\nWorkqueue: events xfrm_state_gc_task\nRIP: xfrm_state_gc_task+0x142/0x650\nModules linked in: esp4_offload xfrm_user [last unloaded: xfrm_iptfs]\nKernel panic - not syncing: Fatal exception","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":"xfrm: clear mode callbacks after failed mode setup","id":"CVE-2026-68415","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"mtd: fix double free and WARN_ON in add_mtd_device() error paths","id":"CVE-2026-68416"},"packages":[],"prev":{"headline":"wifi: cfg80211: cancel sched scan results work on unregister","id":"CVE-2026-68414"},"products":["Linux"],"published":"2026-08-10","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 use-after-free in the Linux kernel xfrm subsystem allows a local attacker to cause a system crash via a kernel panic.","url":"https://insights.sbomify.com/CVE-2026-68415/"}