{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68771 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68771 is a vulnerability in Linux, published on 13 Jan 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-2025-68771 and fix it if it is affected.\n\nWhat it is: CVE-2025-68771 is a vulnerability in Linux, published on 13 Jan 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-2025-68771 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-68771/ (Markdown: https://insights.sbomify.com/CVE-2025-68771/index.md)","id":"CVE-2025-68771","markdown":"https://insights.sbomify.com/CVE-2025-68771/index.md","name":"CVE-2025-68771","record":{"aliases":["BELL-CVE-2025-68771","DEBIAN-CVE-2025-68771","GHSA-48cw-6cgr-r587","ROOT-OS-DEBIAN-11-CVE-2025-68771","ROOT-OS-DEBIAN-12-CVE-2025-68771","ROOT-OS-DEBIAN-13-CVE-2025-68771","ROOT-OS-UBUNTU-2204-CVE-2025-68771","ROOT-OS-UBUNTU-2404-CVE-2025-68771","UBUNTU-CVE-2025-68771"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can trigger a kernel panic in the OCFS2 filesystem by exploiting a null dereference in the allocation chain list handling.","user_interaction":"not_required","vuln_class":"null_dereference"},"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\nocfs2: fix kernel BUG in ocfs2_find_victim_chain\n\nsyzbot reported a kernel BUG in ocfs2_find_victim_chain() because the\n`cl_next_free_rec` field of the allocation chain list (next free slot in\nthe chain list) is 0, triggring the BUG_ON(!cl-\u003ecl_next_free_rec)\ncondition in ocfs2_find_victim_chain() and panicking the kernel.\n\nTo fix this, an if condition is introduced in ocfs2_claim_suballoc_bits(),\njust before calling ocfs2_find_victim_chain(), the code block in it being\nexecuted when either of the following conditions is true:\n\n1. `cl_next_free_rec` is equal to 0, indicating that there are no free\nchains in the allocation chain list\n2. `cl_next_free_rec` is greater than `cl_count` (the total number of\nchains in the allocation chain list)\n\nEither of them being true is indicative of the fact that there are no\nchains left for usage.\n\nThis is addressed using ocfs2_error(), which prints\nthe error log for debugging purposes, rather than panicking the kernel.","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":"ocfs2: fix kernel BUG in ocfs2_find_victim_chain","id":"CVE-2025-68771","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"f2fs: fix to avoid updating compression context during writeback","id":"CVE-2025-68772"},"packages":[],"prev":{"headline":"bnxt_en: Fix XDP_TX path","id":"CVE-2025-68770"},"products":["Linux"],"published":"2026-01-13","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-05-11","vendors":["Linux"]},"summary":"A local attacker can trigger a kernel panic in the OCFS2 filesystem by exploiting a null dereference in the allocation chain list handling.","url":"https://insights.sbomify.com/CVE-2025-68771/"}