{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68341 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68341 is a critical vulnerability in Linux, published on 23 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-68341 and fix it if it is affected.\n\nWhat it is: CVE-2025-68341 is a critical vulnerability in Linux, published on 23 Dec 2025. 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-2025-68341 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-2025-68341/ (Markdown: https://insights.sbomify.com/CVE-2025-68341/index.md)","id":"CVE-2025-68341","markdown":"https://insights.sbomify.com/CVE-2025-68341/index.md","name":"CVE-2025-68341","record":{"aliases":["BELL-CVE-2025-68341","DEBIAN-CVE-2025-68341","GHSA-68w5-72rc-pgrc","UBUNTU-CVE-2025-68341"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel veth driver","requires_auth":"none","summary":"A race condition in the Linux kernel veth driver involving XDP return frames can lead to undefined behavior or potential memory corruption issues.","user_interaction":"not_required","vuln_class":"race_condition"},"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\nveth: reduce XDP no_direct return section to fix race\n\nAs explain in commit fa349e396e48 (\"veth: Fix race with AF_XDP exposing\nold or uninitialized descriptors\") for veth there is a chance after\nnapi_complete_done() that another CPU can manage start another NAPI\ninstance running veth_pool(). For NAPI this is correctly handled as the\nnapi_schedule_prep() check will prevent multiple instances from getting\nscheduled, but for the remaining code in veth_pool() this can run\nconcurrent with the newly started NAPI instance.\n\nThe problem/race is that xdp_clear_return_frame_no_direct() isn't\ndesigned to be nested.\n\nPrior to commit 401cb7dae813 (\"net: Reference bpf_redirect_info via\ntask_struct on PREEMPT_RT.\") the temporary BPF net context\nbpf_redirect_info was stored per CPU, where this wasn't an issue. Since\nthis commit the BPF context is stored in 'current' task_struct. When\nrunning veth in threaded-NAPI mode, then the kthread becomes the storage\narea. Now a race exists between two concurrent veth_pool() function calls\none exiting NAPI and one running new NAPI, both using the same BPF net\ncontext.\n\nRace is when another CPU gets within the xdp_set_return_frame_no_direct()\nsection before exiting veth_pool() calls the clear-function\nxdp_clear_return_frame_no_direct().","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":"veth: reduce XDP no_direct return section to fix race","id":"CVE-2025-68341","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"can: gs_usb: gs_usb_receive_bulk_callback(): check actual_length before accessing data","id":"CVE-2025-68342"},"packages":[],"prev":{"headline":"team: Move team device type change at the end of team_port_add","id":"CVE-2025-68340"},"products":["Linux"],"published":"2025-12-23","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-05","vendors":["Linux"]},"summary":"A race condition in the Linux kernel veth driver involving XDP return frames can lead to undefined behavior or potential memory corruption issues.","url":"https://insights.sbomify.com/CVE-2025-68341/"}