{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68266 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68266 is a memory corruption 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-68266 and fix it if it is affected.\n\nWhat it is: CVE-2025-68266 is a memory corruption 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-68266 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-68266/ (Markdown: https://insights.sbomify.com/CVE-2025-68266/index.md)","id":"CVE-2025-68266","markdown":"https://insights.sbomify.com/CVE-2025-68266/index.md","name":"CVE-2025-68266","record":{"aliases":["BELL-CVE-2025-68266","DEBIAN-CVE-2025-68266","GHSA-cf7w-xh8m-r378","ROOT-OS-DEBIAN-11-CVE-2025-68266","ROOT-OS-DEBIAN-12-CVE-2025-68266","ROOT-OS-DEBIAN-13-CVE-2025-68266","ROOT-OS-UBUNTU-2204-CVE-2025-68266","ROOT-OS-UBUNTU-2404-CVE-2025-68266","UBUNTU-CVE-2025-68266"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A flaw in the Linux kernel's BFS filesystem allows attackers to cause memory corruption or denial of service by mounting a maliciously crafted filesystem image.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\nbfs: Reconstruct file type when loading from disk\n\nsyzbot is reporting that S_IFMT bits of inode-\u003ei_mode can become bogus when\nthe S_IFMT bits of the 32bits \"mode\" field loaded from disk are corrupted\nor when the 32bits \"attributes\" field loaded from disk are corrupted.\n\nA documentation says that BFS uses only lower 9 bits of the \"mode\" field.\nBut I can't find an explicit explanation that the unused upper 23 bits\n(especially, the S_IFMT bits) are initialized with 0.\n\nTherefore, ignore the S_IFMT bits of the \"mode\" field loaded from disk.\nAlso, verify that the value of the \"attributes\" field loaded from disk is\neither BFS_VREG or BFS_VDIR (because BFS supports only regular files and\nthe root directory).","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":"bfs: Reconstruct file type when loading from disk","id":"CVE-2025-68266","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"Privilege escalation in TeamCity","id":"CVE-2025-68267"},"packages":[],"prev":{"headline":"nvme: fix admin request_queue lifetime","id":"CVE-2025-68265"},"products":["Linux"],"published":"2025-12-16","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-15","vendors":["Linux"]},"summary":"A flaw in the Linux kernel's BFS filesystem allows attackers to cause memory corruption or denial of service by mounting a maliciously crafted filesystem image.","url":"https://insights.sbomify.com/CVE-2025-68266/"}