{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72163 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72163 is a 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-72163 and fix it if it is affected.\n\nWhat it is: CVE-2026-72163 is a 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-72163 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-72163/ (Markdown: https://insights.sbomify.com/CVE-2026-72163/index.md)","id":"CVE-2026-72163","markdown":"https://insights.sbomify.com/CVE-2026-72163/index.md","name":"CVE-2026-72163","record":{"aliases":["BELL-CVE-2026-72163","DEBIAN-CVE-2026-72163","GHSA-54g6-8m9x-g4c9","UBUNTU-CVE-2026-72163"],"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":"none","summary":"A local attacker can trigger a kernel panic via direct I/O on unwritten extents in OCFS2, causing a denial of service.","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 NULL h_transaction deref in ocfs2_assure_trans_credits\n\n[BUG]\nA direct write over unwritten extents can panic the kernel in\nocfs2_assure_trans_credits() when the journal aborts during DIO\ncompletion. The crash is a general protection fault from a NULL pointer\ndereference.\n\n[CAUSE]\nocfs2_dio_end_io_write() loops over a direct write's unwritten extents,\nmarking each written under a single journal handle. If the journal\naborts (for example after an I/O error) while the extent tree is being\nupdated, the handle is left aborted with its transaction pointer\ncleared. The extent merge treats that failure as not critical and\nreports success, so the loop keeps using the handle.\nocfs2_assure_trans_credits() reads the handle's remaining credits\nwithout first checking whether the handle is aborted, and that read\ndereferences the cleared transaction pointer.\n\n[FIX]\nA journal abort is recorded in the handle itself, so callers are\nexpected to test the handle rather than rely on a returned error.\nMake ocfs2_assure_trans_credits() do that, as the other ocfs2 journal\nhelpers already do, and return -EROFS when the handle is aborted.","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 NULL h_transaction deref in ocfs2_assure_trans_credits","id":"CVE-2026-72163","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"ocfs2: avoid moving extents to occupied clusters","id":"CVE-2026-72164"},"packages":[],"prev":{"headline":"ocfs2: fix UBSAN array-index-out-of-bounds in ocfs2_sum_rightmost_rec","id":"CVE-2026-72162"},"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 local attacker can trigger a kernel panic via direct I/O on unwritten extents in OCFS2, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2026-72163/"}