# CVE-2026-72161: ocfs2: add journal NULL check in ocfs2_checkpoint_inode()

> A NULL pointer dereference in the Linux kernel OCFS2 filesystem during unmount can cause a system crash, requiring a kernel patch.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72161, DEBIAN-CVE-2026-72161, GHSA-xwjc-q49f-3x92, UBUNTU-CVE-2026-72161

## What is CVE-2026-72161?

CVE-2026-72161 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-72161?


## How do I fix CVE-2026-72161?

Apply the vendor's patch.

## Is CVE-2026-72161 being exploited?

There is no known exploitation of CVE-2026-72161 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72161 and fix it if it is affected.

What it is: CVE-2026-72161 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72161 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72161/ (Markdown: https://insights.sbomify.com/CVE-2026-72161/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72161
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72161
- OSV: https://osv.dev/vulnerability/CVE-2026-72161

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72161/
Summaries are generated and may contain mistakes; the official description above is the record.