CVE-2026-72163 — ocfs2: fix NULL h_transaction deref in ocfs2_assure_trans_credits
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ a68b896aa56e435506453ec8835bc991ec3ae687 and < 2d80e9c56718435a9c9f5f24dbc954989aead579≥ 320273b5649bbcee87f9e65343077189699d2a7a and < 942b818b396c24c452681803ff291552317d2ef1≥ 9ea2d1c6789722d58ec191f14f9a02518d55b6b4 and < 7146d191dae3a8efdb957993fb61a55713186266≥ c05ffb693bfb42a48ef3ee88a55b57392984e111 and < f14aaaa130356ee4adb44de947c098637c70df8f≥ be346c1a6eeb49d8fda827d2a9522124c2f72f36 and < 6ad7532a23bc94076efe9f1486dd7f7493c090ff≥ be346c1a6eeb49d8fda827d2a9522124c2f72f36 and < bd73971fad89d5ee4ea0ba9b92d2ea08733c4a64≥ be346c1a6eeb49d8fda827d2a9522124c2f72f36 and < 253ed993e0b36997ec7b04c1ff76103b38241de2≥ be346c1a6eeb49d8fda827d2a9522124c2f72f36 and < f9ab30c96b0f00c20c6dac93681bdae3a033d229 and 7 moreversion 331d1079d58206ff7dc5518185f800b412f89bc6≥ 5.10.221 and < 5.10.261≥ 5.15.162 and < 5.15.212≥ 6.1.97 and < 6.1.178≥ 6.6.37 and < 6.6.145≥ 6.9.8 and < 6.10version 6.10 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 30, 2026 · 15 reading(s) · max 0.22%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/6ad7532a23bc94076efe9f1486dd7f7493c090ff
- git.kernel.org/stable/c/942b818b396c24c452681803ff291552317d2ef1
- git.kernel.org/stable/c/f9ab30c96b0f00c20c6dac93681bdae3a033d229
- git.kernel.org/stable/c/2d80e9c56718435a9c9f5f24dbc954989aead579
- git.kernel.org/stable/c/f14aaaa130356ee4adb44de947c098637c70df8f
- git.kernel.org/stable/c/7146d191dae3a8efdb957993fb61a55713186266
- git.kernel.org/stable/c/bd73971fad89d5ee4ea0ba9b92d2ea08733c4a64
- git.kernel.org/stable/c/253ed993e0b36997ec7b04c1ff76103b38241de2
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-72163 is "ocfs2: fix NULL h_transaction deref in ocfs2_assure_trans_credits", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.