{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98800 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98800 is an use after free vulnerability in Linux, published on 18 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-98800 and fix it if it is affected.\n\nWhat it is: CVE-2026-98800 is an use after free vulnerability in Linux, published on 18 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-98800 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-98800/ (Markdown: https://insights.sbomify.com/CVE-2026-98800/index.md)","id":"CVE-2026-98800","markdown":"https://insights.sbomify.com/CVE-2026-98800/index.md","name":"CVE-2026-98800","record":{"aliases":["AZL-108831","BELL-CVE-2026-98800","DEBIAN-CVE-2026-98800","GHSA-hw45-3jc9-w8mr","UBUNTU-CVE-2026-98800"],"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":"high_privilege","summary":"A use-after-free in the Linux kernel BPF trampoline allows local attackers with high privileges to execute arbitrary code or escalate privileges.","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\nbpf: Wait for an RCU tasks grace period before freeing trampoline progs\n\nWhen a prog is detached from a trampoline, it is freed after an RCU\ngrace period, or an RCU tasks trace one if it is sleepable. This covers\nthe tasks that are running the prog, since the prog's enter helper takes\nthe matching read lock before the prog is called. On a preemptible\nkernel, it doesn't cover a task that was preempted in the trampoline\njust before the enter helper. That task holds no lock yet, and it calls\nthe prog after it was freed:\n\n  BUG: KASAN: vmalloc-out-of-bounds in __bpf_prog_enter_recur+0x3a5/0x3f0\n  Read of size 8 at addr ffffc90000055040 by task candidate/110\n  CPU: 1 UID: 0 PID: 110 Comm: candidate Not tainted 7.3.0-rc2-00014-g15071f2a1263-dirty #2 PREEMPT(full)\n  Call Trace:\n   \u003cTASK\u003e\n   __bpf_prog_enter_recur+0x3a5/0x3f0\n   bpf_trampoline_6442509193+0x37/0xf1\n   __x64_sys_futex+0x9/0x410\n   do_syscall_64+0xb0/0x530\n   ...\n\nWait for an RCU tasks grace period before the existing one when freeing\na prog that was linked to a trampoline. An RCU tasks grace period only\nends once the tasks that were preempted have run again, and\nbpf_tramp_image_put() already relies on it to free the image. It doesn't\nwait for tasks that sleep in the trampoline, the next commit takes care\nof those.\n\nOnly progs that were linked to a trampoline can be called this way, so\nbpf_trampoline_add_prog() marks them and other progs are still freed as\nbefore.","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":"bpf: Wait for an RCU tasks grace period before freeing trampoline progs","id":"CVE-2026-98800","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"net: restrict SO_RESERVE_MEM to TCP sockets and cap max value","id":"CVE-2026-98801"},"packages":[],"prev":{"headline":"bpf: Skip detached progs in trampoline images that are still in use","id":"CVE-2026-98799"},"products":["Linux"],"published":"2026-10-18","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 use-after-free in the Linux kernel BPF trampoline allows local attackers with high privileges to execute arbitrary code or escalate privileges.","url":"https://insights.sbomify.com/CVE-2026-98800/"}