# CVE-2023-54192: f2fs: fix null pointer panic in tracepoint in __replace_atomic_write_block

> A local attacker can trigger a kernel panic via a null pointer dereference in the f2fs filesystem, causing a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Dec 2025
- **Updated:** 23 May 2026
- **Also known as:** BELL-CVE-2023-54192, DEBIAN-CVE-2023-54192, GHSA-x38v-9849-rp33, UBUNTU-CVE-2023-54192

## What is CVE-2023-54192?

CVE-2023-54192 is a vulnerability in Linux, published on 30 Dec 2025. 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:

f2fs: fix null pointer panic in tracepoint in __replace_atomic_write_block

We got a kernel panic if old_addr is NULL.

https://bugzilla.kernel.org/show_bug.cgi?id=217266

BUG: kernel NULL pointer dereference, address: 0000000000000000
 Call Trace:
  <TASK>
  f2fs_commit_atomic_write+0x619/0x990 [f2fs a1b985b80f5babd6f3ea778384908880812bfa43]
  __f2fs_ioctl+0xd8e/0x4080 [f2fs a1b985b80f5babd6f3ea778384908880812bfa43]
  ? vfs_write+0x2ae/0x3f0
  ? vfs_write+0x2ae/0x3f0
  __x64_sys_ioctl+0x91/0xd0
  do_syscall_64+0x5c/0x90
  entry_SYSCALL_64_after_hwframe+0x72/0xdc
 RIP: 0033:0x7f69095fe53f

## Which versions are affected by CVE-2023-54192?


## How do I fix CVE-2023-54192?

Apply the vendor's patch.

## Is CVE-2023-54192 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-54192 and fix it if it is affected.

What it is: CVE-2023-54192 is a vulnerability in Linux, published on 30 Dec 2025. 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-2023-54192 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-2023-54192/ (Markdown: https://insights.sbomify.com/CVE-2023-54192/index.md)
```

## Sources

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

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