CVE-2026-72161

ocfs2: add journal NULL check in ocfs2_checkpoint_inode()

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: add journal NULL check in ocfs2_checkpoint_inode() During unmount, ocfs2_journal_shutdown() frees the journal and sets osb->journal to NULL. Later, when VFS evicts remaining cached inodes, ocfs2_evict_inode() -> ocfs2_clear_inode() -> ocfs2_checkpoint_inode() -> ocfs2_ci_fully_checkpointed() dereferences osb->journal, causing a NULL pointer dereference. Fix this by adding a NULL check for osb->journal in ocfs2_checkpoint_inode(). If the journal is NULL, it has already been fully flushed and destroyed during shutdown, so there is nothing to checkpoint.

Affected

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

5.16 ≤ v < 6.1.1785.16 ≤ v < 6.12.975.16 ≤ v < 6.18.405.16 ≤ v < 6.6.1455.16 ≤ v < 7.1.55.16 ≤ v < 7.25.16da5e7c87827e8caa6a1eeec6d95dcf74ab592a01
Vendor states this is fixed in 24daf13422e8328fd588c34a017bdef1949910e8 (fixed)
Vendor states this is fixed in 499714de42ab4d2e778cbb10186684142a1222eb (fixed)
Vendor states this is fixed in 63921f790234b221e4b15c56c72888b13250f81d (fixed)
Vendor states this is fixed in 7da7e4ac21895fe34cceffcfc99497cc2750da99 (fixed)
Vendor states this is fixed in a291c77c034b7a81849ce9b71cc9ecda9e587d89 (fixed)
Vendor states this is fixed in eb6a13834c23e291f1170cb1b489ec255edfa5a3 (fixed)
Vendor states this is fixed in 5.16 (unaffected)
Vendor states this is fixed in 6.1.178 (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