{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68315 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68315 is a critical denial of service vulnerability in Linux, published on 16 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-68315 and fix it if it is affected.\n\nWhat it is: CVE-2025-68315 is a critical denial of service vulnerability in Linux, published on 16 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-68315 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-68315/ (Markdown: https://insights.sbomify.com/CVE-2025-68315/index.md)","id":"CVE-2025-68315","markdown":"https://insights.sbomify.com/CVE-2025-68315/index.md","name":"CVE-2025-68315","record":{"aliases":["BELL-CVE-2025-68315","DEBIAN-CVE-2025-68315","GHSA-9w55-r5pp-5hfx","ROOT-OS-DEBIAN-11-CVE-2025-68315","ROOT-OS-DEBIAN-12-CVE-2025-68315","ROOT-OS-DEBIAN-13-CVE-2025-68315","ROOT-OS-UBUNTU-2204-CVE-2025-68315","ROOT-OS-UBUNTU-2404-CVE-2025-68315","UBUNTU-CVE-2025-68315"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel filesystem","requires_auth":"none","summary":"A missing sanity check in the f2fs filesystem allows corrupted node IDs to cause system instability or crashes.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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\nf2fs: fix to detect potential corrupted nid in free_nid_list\n\nAs reported, on-disk footer.ino and footer.nid is the same and\nout-of-range, let's add sanity check on f2fs_alloc_nid() to detect\nany potential corruption in free_nid_list.","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":"f2fs: fix to detect potential corrupted nid in free_nid_list","id":"CVE-2025-68315","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"scsi: ufs: core: Fix invalid probe error return value","id":"CVE-2025-68316"},"packages":[],"prev":{"headline":"drm/msm: make sure last_fence is always updated","id":"CVE-2025-68314"},"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-05","vendors":["Linux"]},"summary":"A missing sanity check in the f2fs filesystem allows corrupted node IDs to cause system instability or crashes.","url":"https://insights.sbomify.com/CVE-2025-68315/"}