CVE-2023-53429
Last modified
CVE-2023-53429 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: btrfs: don't check PageError in __extent_writepage __extent_writepage currenly sets PageError whenever any error happens, and the also checks for PageError to decide if to call error handling. This leads to very unclear responsibility for cleaning up on errors. In the VM and generic writeback helpers the basic idea is that once I/O is fired off all error handling responsibility is delegated to the end I/O handler. But if that end I/O handler sets the PageError bit, and the submitter checks it, the bit could in some cases leak into the submission context for fast enough I/O. Fix this by simply not checking PageError and just using the local ret variable to check for submission errors. EPSS estimates a 0.12% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: btrfs: don't check PageError in __extent_writepage __extent_writepage currenly sets PageError whenever any error happens, and the also checks for PageError to decide if to call error handling. This leads to very unclear responsibility for cleaning up on errors. In the VM and generic writeback helpers the basic idea is that once I/O is fired off all error handling responsibility is delegated to the end I/O handler. But if that end I/O handler sets the PageError bit, and the submitter checks it, the bit could in some cases leak into the submission context for fast enough I/O. Fix this by simply not checking PageError and just using the local ret variable to check for submission errors. This also fundamentally solves the long problem documented in a comment in __extent_writepage by never leaking the error bit into the submission context.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | < 6.4.7 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2023-53429?
How severe is CVE-2023-53429?
How do I fix CVE-2023-53429?
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-53423In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53424In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53425In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53426In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53427In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53428In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-5343The Popup box WordPress plugin before 3.7.9 does not sanitis…4.8
- CVE-2023-53430In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53431In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53432In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53433In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53434In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2023-53429?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
