CVE-2023-53429 Details
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.
A vulnerability in the Linux kernel's Btrfs file system has been addressed, specifically related to how PageError is managed during the writeback process. The issue arose because the __extent_writepage function would set the PageError bit whenever an error occurred, and subsequently check this bit to determine whether to initiate error handling. This created confusion regarding who was responsible for managing errors. In the virtual memory and generic writeback helpers, once input/output operations are initiated, the duty of handling errors is passed to the final I/O handler. However, if this handler sets the PageError bit and the original caller checks it, the error could unintentionally transfer back into the submission context, particularly with fast I/O operations. The vulnerability has been fixed by eliminating the check for PageError and instead relying on a local variable to track submission errors, preventing the error bit from leaking into the submission context.
Users can upgrade to the latest version of the Linux kernel where this vulnerability has been addressed. Instructions for downloading the patched version are available on the Linux kernel's official website.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jan 14, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/3e92499e3b004baffb479d61e191b41b604ece9a | kernel.org | Patch |
| https://git.kernel.org/stable/c/d40be032ecd8ee1ca033bee43c7755d21fb4d72a | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | < 6.4.7 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Aug 4, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jan 14, 2026 | CVE Modified | CISA-ADP |
| Dec 11, 2025 | Initial Analysis | [email protected] |
| Sep 18, 2025 | New CVE Received | kernel.org |