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.
- 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
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
Which versions are affected by CVE-2023-53081?
It affects 1 product.
Products include Linux kernel.
How do I fix CVE-2023-53081?
Apply the vendor's patch.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
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
Sources
Also known as BELL-CVE-2023-53081, DEBIAN-CVE-2023-53081, GHSA-8gx6-v9p7-fr2f, UBUNTU-CVE-2023-53081.