{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72160 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72160 is a high-severity memory corruption vulnerability in Linux, published on 15 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-72160 and fix it if it is affected.\n\nWhat it is: CVE-2026-72160 is a high-severity memory corruption vulnerability in Linux, published on 15 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-72160 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-2026-72160/ (Markdown: https://insights.sbomify.com/CVE-2026-72160/index.md)","id":"CVE-2026-72160","markdown":"https://insights.sbomify.com/CVE-2026-72160/index.md","name":"CVE-2026-72160","record":{"aliases":["BELL-CVE-2026-72160","DEBIAN-CVE-2026-72160","GHSA-42g7-hf2f-vfr8","UBUNTU-CVE-2026-72160"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel OCFS2","requires_auth":"low_privilege","summary":"Attackers can trigger memory corruption or crashes by mounting a crafted OCFS2 filesystem with invalid inode mode bits, requiring kernel patches.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/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\nocfs2: reject dinodes with non-canonical i_mode type\n\nPatch series \"ocfs2: harden inode validators against forged metadata\", v2.\n\nThis series adds three structural checks to OCFS2 dinode validation so\nmalformed on-disk fields are rejected before ocfs2_populate_inode() copies\nthem into the in-core inode.\n\nThe checks cover:\n\n  - i_mode values whose type bits do not name a canonical POSIX file\n    type;\n  - non-device dinodes whose id1.dev1.i_rdev field is non-zero; and\n  - non-inline dinodes that claim non-zero i_size while i_clusters is\n    zero, covering directories unconditionally and regular files on\n    non-sparse volumes.\n\nThe normal read path reports these through ocfs2_error(), matching the\nexisting suballoc-slot, inline-data, chain-list, and refcount checks.  The\nonline filecheck path uses the same structural predicates but keeps its\nown reporting contract, returning OCFS2_FILECHECK_ERR_INVALIDINO instead\nof calling ocfs2_error().\n\nThis patch (of 3):\n\nocfs2_validate_inode_block() currently accepts any non-zero i_mode value. \nocfs2_populate_inode() then copies that mode verbatim into inode-\u003ei_mode\nand dispatches on i_mode \u0026 S_IFMT to the file/dir/symlink/special_file\niops; an unrecognised type falls through to ocfs2_special_file_iops and\ninit_special_inode().\n\nReject dinodes whose type bits do not name one of the seven canonical\nPOSIX file types.  Use fs_umode_to_ftype(), the same generic file-type\nconversion helper OCFS2 already uses for directory entries, so the\naccepted inode type set matches the kernel file-type vocabulary instead of\nopen-coding a local switch.\n\nApply the same structural check to the online filecheck read path. \nfilecheck keeps its own error namespace, so it reports malformed i_mode\nthrough the filecheck logger and OCFS2_FILECHECK_ERR_INVALIDINO instead of\ncalling ocfs2_error(), but it must not allow a malformed dinode to proceed\ninto ocfs2_populate_inode().","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: reject dinodes with non-canonical i_mode type","id":"CVE-2026-72160","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"ocfs2: add journal NULL check in ocfs2_checkpoint_inode()","id":"CVE-2026-72161"},"packages":[],"prev":{"headline":"ocfs2: reject non-inline dinodes with i_size and zero i_clusters","id":"CVE-2026-72159"},"products":["Linux"],"published":"2026-08-15","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-16","vendors":["Linux"]},"summary":"Attackers can trigger memory corruption or crashes by mounting a crafted OCFS2 filesystem with invalid inode mode bits, requiring kernel patches.","url":"https://insights.sbomify.com/CVE-2026-72160/"}