{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98231 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98231 is an use after free vulnerability in Linux, published on 6 Oct 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-98231 and fix it if it is affected.\n\nWhat it is: CVE-2026-98231 is an use after free vulnerability in Linux, published on 6 Oct 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-98231 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-98231/ (Markdown: https://insights.sbomify.com/CVE-2026-98231/index.md)","id":"CVE-2026-98231","markdown":"https://insights.sbomify.com/CVE-2026-98231/index.md","name":"CVE-2026-98231","record":{"aliases":["AZL-106323","BELL-CVE-2026-98231","DEBIAN-CVE-2026-98231","GHSA-8c3r-c85m-88vq","UBUNTU-CVE-2026-98231"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel xfrm subsystem allows local attackers to trigger a use-after-free, potentially leading to privilege escalation or code execution.","user_interaction":"not_required","vuln_class":"use_after_free"},"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\nxfrm: serialize state GC with device state flush\n\nThe deferred-device pass in xfrm_dev_state_flush() finds states under\nxfrm_state_dev_gc_lock, but drops the lock before calling\nxfrm_dev_state_free() because the driver callback may sleep.  The device\nGC list does not hold an xfrm_state reference, so the state GC worker can\ndestroy the same state concurrently.\n\nThe race can proceed as follows:\n\n  CPU 0                               CPU 1\n  find x on the device GC list\n  drop xfrm_state_dev_gc_lock\n  read x-\u003exso.dev\n                                      xfrm_state_gc_destroy(x)\n                                      xfrm_dev_state_free(x)\n                                      xfrm_state_free(x)\n  continue xfrm_dev_state_free(x)\n\nBoth paths can invoke the driver callback and drop the device reference.\nCPU 0 can also access the xfrm_state after CPU 1 has freed it.\n\nKASAN reported:\n\n  BUG: KASAN: slab-use-after-free in xfrm_dev_state_free+0x24c/0x2a0\n  Read of size 8 at addr ffff88810bbaa960 by task poc/102\n\n  Call Trace:\n   xfrm_dev_state_free+0x24c/0x2a0\n   xfrm_dev_state_flush+0x353/0x400\n   xfrm_dev_event+0x26d/0x3a0\n   notifier_call_chain+0xc0/0x280\n   __dev_notify_flags+0x169/0x250\n   netif_change_flags+0xe7/0x160\n   dev_change_flags+0x96/0x220\n   devinet_ioctl+0x7f4/0x1880\n\n  Allocated by task 87:\n   xfrm_state_alloc+0x1e/0x5c0\n   xfrm_add_sa+0xe7f/0x5820\n   xfrm_user_rcv_msg+0x4f3/0x940\n\n  Freed by task 57:\n   kmem_cache_free+0xcb/0x3d0\n   xfrm_state_gc_task+0x4a8/0x650\n   process_one_work+0x63a/0x1070\n\nSerialize xfrm_state destruction against the deferred-device pass with a\nmutex.  Keep xfrm_state_dev_gc_lock limited to list operations and retain\nthe existing callback and device-reference release ordering.","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: serialize state GC with device state flush","id":"CVE-2026-98231","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"scsi: core: Validate MODE SENSE lengths in scsi_cdl_enable()","id":"CVE-2026-98232"},"packages":[],"prev":{"headline":"xfrm: use hlist_del_init_rcu for state_cache and state_cache_input","id":"CVE-2026-98230"},"products":["Linux"],"published":"2026-10-06","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":"A race condition in the Linux kernel xfrm subsystem allows local attackers to trigger a use-after-free, potentially leading to privilege escalation or code execution.","url":"https://insights.sbomify.com/CVE-2026-98231/"}