{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68317 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68317 is a high-severity vulnerability in Linux, published on 16 Dec 2025. 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-2025-68317 and fix it if it is affected.\n\nWhat it is: CVE-2025-68317 is a high-severity vulnerability in Linux, published on 16 Dec 2025. 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-2025-68317 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-68317/ (Markdown: https://insights.sbomify.com/CVE-2025-68317/index.md)","id":"CVE-2025-68317","markdown":"https://insights.sbomify.com/CVE-2025-68317/index.md","name":"CVE-2025-68317","record":{"aliases":["BELL-CVE-2025-68317","DEBIAN-CVE-2025-68317","GHSA-7p3q-9c8m-84x3","ROOT-OS-UBUNTU-2204-CVE-2025-68317","ROOT-OS-UBUNTU-2404-CVE-2025-68317","UBUNTU-CVE-2025-68317"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"The Linux kernel io_uring zero-copy notification context check was added to prevent potential issues in chained notification handling.","user_interaction":"not_required","vuln_class":"other"},"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\nio_uring/zctx: check chained notif contexts\n\nSend zc only links ubuf_info for requests coming from the same context.\nThere are some ambiguous syz reports, so let's check the assumption on\nnotification completion.","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":"io_uring/zctx: check chained notif contexts","id":"CVE-2025-68317","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"clk: thead: th1520-ap: set all AXI clocks to CLK_IS_CRITICAL","id":"CVE-2025-68318"},"packages":[],"prev":{"headline":"scsi: ufs: core: Fix invalid probe error return value","id":"CVE-2025-68316"},"products":["Linux"],"published":"2025-12-16","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["Linux"]},"summary":"The Linux kernel io_uring zero-copy notification context check was added to prevent potential issues in chained notification handling.","url":"https://insights.sbomify.com/CVE-2025-68317/"}