CVE-2023-53081
Last modified
CVE-2023-53081 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.9.242, < 4.10 | — |
| Linux | Linux Kernel | >= 4.14.204, < 4.14.312 | — |
| Linux | Linux Kernel | >= 4.19.155, < 4.19.280 | — |
| Linux | Linux Kernel | >= 5.4.75, < 5.4.240 | — |
| Linux | Linux Kernel | >= 5.9.5, < 5.10.177 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.105 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.21 | — |
| Linux | Linux Kernel | >= 6.2, < 6.2.8 | — |
| Linux | Linux Kernel | 6.3 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2023-53081?
How severe is CVE-2023-53081?
How do I fix CVE-2023-53081?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-53076Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2023-53077In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53078In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53079In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-5308The Podcast Subscribe Buttons plugin for WordPress is vulner…5.4
- CVE-2023-53080In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53082In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53083In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53084In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53085In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2023-53086In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53087In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2023-53081?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST