ocfs2: add journal NULL check in ocfs2_checkpoint_inode()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ da5e7c87827e8caa6a1eeec6d95dcf74ab592a01 · < a291c77c034b7a81849ce9b71cc9ecda9e587d89| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
During unmount, ocfs2 can dereference a journal pointer after the journal has been freed, potentially crashing the kernel. The input does not establish an attacker path, authentication requirement, or user-interaction requirement.
Operators running Linux kernels with ocfs2 should check their exposure; affected versions are not specified.