CVE-2026-72163: ocfs2: fix NULL h_transaction deref in ocfs2_assure_trans_credits
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 253ed993e0b36997ec7b04c1ff76103b38241de2, 2d80e9c56718435a9c9f5f24dbc954989aead579, 5.10.261.
Low priority for now. Upgrade to Linux Linux 253ed993e0b36997ec7b04c1ff76103b38241de2, 2d80e9c56718435a9c9f5f24dbc954989aead579, 5.10.261 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 15, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 331d1079d58206ff7dc5518185f800b412f89bc6, 6.10affected
- a68b896aa56e435506453ec8835bc991ec3ae687 and later · before 2d80e9c56718435a9c9f5f24dbc954989aead579affected · git
- 320273b5649bbcee87f9e65343077189699d2a7a and later · before 942b818b396c24c452681803ff291552317d2ef1affected · git
- 9ea2d1c6789722d58ec191f14f9a02518d55b6b4 and later · before 7146d191dae3a8efdb957993fb61a55713186266affected · git
- c05ffb693bfb42a48ef3ee88a55b57392984e111 and later · before f14aaaa130356ee4adb44de947c098637c70df8faffected · git
- be346c1a6eeb49d8fda827d2a9522124c2f72f36 and later · before 6ad7532a23bc94076efe9f1486dd7f7493c090ffaffected · git
- be346c1a6eeb49d8fda827d2a9522124c2f72f36 and later · before bd73971fad89d5ee4ea0ba9b92d2ea08733c4a64affected · git
- be346c1a6eeb49d8fda827d2a9522124c2f72f36 and later · before 253ed993e0b36997ec7b04c1ff76103b38241de2affected · git
- be346c1a6eeb49d8fda827d2a9522124c2f72f36 and later · before f9ab30c96b0f00c20c6dac93681bdae3a033d229affected · git
- 5.10.221 and later · before 5.10.261affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72160Aug 15, 2026 · ocfs2: reject dinodes with non-canonical i_mode type35Monitor
- ← EarlierCVE-2026-72162Aug 15, 2026 · ocfs2: fix UBSAN array-index-out-of-bounds in ocfs2_sum_rightmost_rec31Monitor
- Later →CVE-2026-72164Aug 15, 2026 · ocfs2: avoid moving extents to occupied clusters31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 253ed993e0b36997ec7b04c1ff76103b38241de2 | Vendor (CNA) |
| Linux Linux | 2d80e9c56718435a9c9f5f24dbc954989aead579 | Vendor (CNA) |
| Linux Linux | 5.10.261 | Vendor (CNA) |
| Linux Linux | 5.15.212 | Vendor (CNA) |
| Linux Linux | 6.1.178 | Vendor (CNA) |
| Linux Linux | 6.10 | Vendor (CNA) |
| Linux Linux | 6.6.145 | Vendor (CNA) |
| Linux Linux | 6ad7532a23bc94076efe9f1486dd7f7493c090ff | Vendor (CNA) |
| Linux Linux | 7146d191dae3a8efdb957993fb61a55713186266 | Vendor (CNA) |
| Linux Linux | 942b818b396c24c452681803ff291552317d2ef1 | Vendor (CNA) |
| Linux Linux | bd73971fad89d5ee4ea0ba9b92d2ea08733c4a64 | Vendor (CNA) |
| Linux Linux | f14aaaa130356ee4adb44de947c098637c70df8f | Vendor (CNA) |
| Linux Linux | f9ab30c96b0f00c20c6dac93681bdae3a033d229 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2d80e9c56718435a9c9f5f24dbc954989aead579
- git.kernel.org/stable/c/6ad7532a23bc94076efe9f1486dd7f7493c090ff
- git.kernel.org/stable/c/7146d191dae3a8efdb957993fb61a55713186266
- git.kernel.org/stable/c/942b818b396c24c452681803ff291552317d2ef1
- git.kernel.org/stable/c/bd73971fad89d5ee4ea0ba9b92d2ea08733c4a64
- git.kernel.org/stable/c/f14aaaa130356ee4adb44de947c098637c70df8f
- git.kernel.org/stable/c/f9ab30c96b0f00c20c6dac93681bdae3a033d229
Vendor advisories and official records. Exploit/PoC links are deliberately left out.