CVE-2026-72163

ocfs2: fix NULL h_transaction deref in ocfs2_assure_trans_credits

N/A
Published: August 15, 2026 at 05:53 AM UTC
Updated: August 17, 2026 at 06:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix NULL h_transaction deref in ocfs2_assure_trans_credits [BUG] A direct write over unwritten extents can panic the kernel in ocfs2_assure_trans_credits() when the journal aborts during DIO completion. The crash is a general protection fault from a NULL pointer dereference. [CAUSE] ocfs2_dio_end_io_write() loops over a direct write's unwritten extents, marking each written under a single journal handle. If the journal aborts (for example after an I/O error) while the extent tree is being updated, the handle is left aborted with its transaction pointer cleared. The extent merge treats that failure as not critical and reports success, so the loop keeps using the handle. ocfs2_assure_trans_credits() reads the handle's remaining credits without first checking whether the handle is aborted, and that read dereferences the cleared transaction pointer. [FIX] A journal abort is recorded in the handle itself, so callers are expected to test the handle rather than rely on a returned error. Make ocfs2_assure_trans_credits() do that, as the other ocfs2 journal helpers already do, and return -EROFS when the handle is aborted.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 6.9.85.10.221 ≤ v < 5.10.2615.15.162 ≤ v < 5.15.2126.1.97 ≤ v < 6.1.1786.10 ≤ v < 6.12.976.10 ≤ v < 6.18.406.10 ≤ v < 7.1.56.10 ≤ v < 7.26.6.37 ≤ v < 6.6.1456.9.8 ≤ v < 6.10320273b5649bbcee87f9e65343077189699d2a7a331d1079d58206ff7dc5518185f800b412f89bc65.10.2215.15.1626.1.976.106.6.376.9.89ea2d1c6789722d58ec191f14f9a02518d55b6b4a68b896aa56e435506453ec8835bc991ec3ae687be346c1a6eeb49d8fda827d2a9522124c2f72f36c05ffb693bfb42a48ef3ee88a55b57392984e111
Vendor states this is fixed in 253ed993e0b36997ec7b04c1ff76103b38241de2 (fixed)
Vendor states this is fixed in 2d80e9c56718435a9c9f5f24dbc954989aead579 (fixed)
Vendor states this is fixed in 6ad7532a23bc94076efe9f1486dd7f7493c090ff (fixed)
Vendor states this is fixed in 7146d191dae3a8efdb957993fb61a55713186266 (fixed)
Vendor states this is fixed in 942b818b396c24c452681803ff291552317d2ef1 (fixed)
Vendor states this is fixed in bd73971fad89d5ee4ea0ba9b92d2ea08733c4a64 (fixed)
Vendor states this is fixed in f14aaaa130356ee4adb44de947c098637c70df8f (fixed)
Vendor states this is fixed in f9ab30c96b0f00c20c6dac93681bdae3a033d229 (fixed)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.10 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card