{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68767 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68767 is a memory corruption vulnerability in Linux, published on 13 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-68767 and fix it if it is affected.\n\nWhat it is: CVE-2025-68767 is a memory corruption vulnerability in Linux, published on 13 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-68767 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-68767/ (Markdown: https://insights.sbomify.com/CVE-2025-68767/index.md)","id":"CVE-2025-68767","markdown":"https://insights.sbomify.com/CVE-2025-68767/index.md","name":"CVE-2025-68767","record":{"aliases":["AZL-74315","BELL-CVE-2025-68767","DEBIAN-CVE-2025-68767","GHSA-mgmc-76vj-qf3j","ROOT-OS-DEBIAN-11-CVE-2025-68767","ROOT-OS-DEBIAN-12-CVE-2025-68767","ROOT-OS-DEBIAN-13-CVE-2025-68767","ROOT-OS-UBUNTU-2204-CVE-2025-68767","ROOT-OS-UBUNTU-2404-CVE-2025-68767","UBUNTU-CVE-2025-68767"],"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 local attacker can cause memory corruption or system crash by mounting a maliciously crafted HFS+ filesystem with invalid inode modes.","user_interaction":"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\nhfsplus: Verify inode mode 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 16bits \"mode\" field loaded from disk are corrupted.\n\nAccording to [1], the permissions field was treated as reserved in Mac OS\n8 and 9. According to [2], the reserved field was explicitly initialized\nwith 0, and that field must remain 0 as long as reserved. Therefore, when\nthe \"mode\" field is not 0 (i.e. no longer reserved), the file must be\nS_IFDIR if dir == 1, and the file must be one of S_IFREG/S_IFLNK/S_IFCHR/\nS_IFBLK/S_IFIFO/S_IFSOCK if dir == 0.","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":"hfsplus: Verify inode mode when loading from disk","id":"CVE-2025-68767","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":"inet: frags: flush pending skbs in fqdir_pre_exit()","id":"CVE-2025-68768"},"packages":[],"prev":{"headline":"irqchip/mchp-eic: Fix error code in mchp_eic_domain_alloc()","id":"CVE-2025-68766"},"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 cause memory corruption or system crash by mounting a maliciously crafted HFS+ filesystem with invalid inode modes.","url":"https://insights.sbomify.com/CVE-2025-68767/"}