# CVE-2023-53081: ocfs2: fix data corruption after failed write

> A flaw in the Linux kernel OCFS2 filesystem can cause data corruption and loss when a buffered write fails, requiring a kernel patch.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 2 May 2025
- **Updated:** 23 May 2026
- **Also known as:** BELL-CVE-2023-53081, DEBIAN-CVE-2023-53081, GHSA-8gx6-v9p7-fr2f, UBUNTU-CVE-2023-53081

## What is CVE-2023-53081?

CVE-2023-53081 is a high-severity memory corruption vulnerability in Linux kernel, published on 2 May 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:

ocfs2: fix data corruption after failed write

When buffered write fails to copy data into underlying page cache page,
ocfs2_write_end_nolock() just zeroes out and dirties the page.  This can
leave dirty page beyond EOF and if page writeback tries to write this page
before write succeeds and expands i_size, page gets into inconsistent
state where page dirty bit is clear but buffer dirty bits stay set
resulting in page data never getting written and so data copied to the
page is lost.  Fix the problem by invalidating page beyond EOF after
failed write.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2023-53081 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-53081 is a high-severity memory corruption vulnerability in Linux kernel, published on 2 May 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-53081 in the wild and no public exploit code.

Affected product: Linux kernel. 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-53081/ (Markdown: https://insights.sbomify.com/CVE-2023-53081/index.md)
```

## Sources

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

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