{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72159 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72159 is a denial of service vulnerability in Linux, published on 15 Aug 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-2026-72159 and fix it if it is affected.\n\nWhat it is: CVE-2026-72159 is a denial of service vulnerability in Linux, published on 15 Aug 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-2026-72159 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-72159/ (Markdown: https://insights.sbomify.com/CVE-2026-72159/index.md)","id":"CVE-2026-72159","markdown":"https://insights.sbomify.com/CVE-2026-72159/index.md","name":"CVE-2026-72159","record":{"aliases":["BELL-CVE-2026-72159","DEBIAN-CVE-2026-72159","GHSA-5wh8-rgp3-6j39","UBUNTU-CVE-2026-72159"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel filesystem","requires_auth":"none","summary":"A malformed OCFS2 directory inode can cause a denial of service by forcing infinite loops during directory traversal when sparse allocation is disabled.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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: reject non-inline dinodes with i_size and zero i_clusters\n\nOn a volume mounted without OCFS2_FEATURE_INCOMPAT_SPARSE_ALLOC, a\nnon-inline regular file with non-zero i_size and zero i_clusters is\nstructurally malformed: the extent map declares no allocated clusters yet\nthe size header claims content exists.  Keep rejecting that shape, but\nexpress it through a shared predicate so the same invariant is available\nto normal inode reads and online filecheck.\n\nThe same zero-cluster shape is also malformed for non-inline directories. \nocfs2 directory growth allocates backing storage before advancing i_size,\nand ocfs2_dir_foreach_blk_el() later walks until ctx-\u003epos reaches\ni_size_read(inode).  A forged directory dinode with a huge i_size and no\nclusters would repeatedly fail on holes while advancing through the\nclaimed size.\n\nSparse regular files remain exempt: on sparse-alloc volumes, truncate can\nlegitimately grow i_size without allocating clusters.  System inodes and\ninline-data dinodes also retain their separate storage rules.\n\nMirror the check in ocfs2_filecheck_validate_inode_block() as well. \nfilecheck reports through its own error namespace, so malformed\nsize/cluster state is logged as a filecheck invalid-inode result rather\nthan via ocfs2_error(), but it must not proceed into\nocfs2_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 non-inline dinodes with i_size and zero i_clusters","id":"CVE-2026-72159","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"ocfs2: reject dinodes with non-canonical i_mode type","id":"CVE-2026-72160"},"packages":[],"prev":{"headline":"fpga: dfl: add bounds check in dfh_get_param_size()","id":"CVE-2026-72158"},"products":["Linux"],"published":"2026-08-15","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-08-17","vendors":["Linux"]},"summary":"A malformed OCFS2 directory inode can cause a denial of service by forcing infinite loops during directory traversal when sparse allocation is disabled.","url":"https://insights.sbomify.com/CVE-2026-72159/"}