CVE-2023-53820 Details
Description
In the Linux kernel, the following vulnerability has been resolved: loop: loop_set_status_from_info() check before assignment In loop_set_status_from_info(), lo->lo_offset and lo->lo_sizelimit should be checked before reassignment, because if an overflow error occurs, the original correct value will be changed to the wrong value, and it will not be changed back. More, the original patch did not solve the problem, the value was set and ioctl returned an error, but the subsequent io used the value in the loop driver, which still caused an alarm: loop_handle_cmd do_req_filebacked loff_t pos = ((loff_t) blk_rq_pos(rq) << 9) + lo->lo_offset; lo_rw_aio cmd->iocb.ki_pos = pos
A vulnerability has been identified in the Linux kernel's loop device management. The issue arises in the function 'loop_set_status_from_info()', where the parameters 'lo->lo_offset' and 'lo->lo_sizelimit' are not properly validated before being reassigned. This oversight can lead to an overflow error, causing the original, correct values to be replaced with incorrect ones, without a mechanism to revert them. Although an initial patch attempted to address this issue, it fell short. The patch set a value and returned an error, but the loop driver continued to use the erroneous value, triggering an alarm. This vulnerability affects the stable branch of the Linux kernel.
Users can update to the latest version of the Linux kernel where this vulnerability has been patched. Instructions for updating the kernel can be found in the official Linux documentation.
Metrics
CVSS 4.0 Severity and Vector Strings:
VolerionCVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Dec 9, 2025References 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/258809bf22bf71d53247856f374f2b1d055f2fd4 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/2ea7077748e5d7cc64f1c31342c802fe66ea7426 | kernel.org | |
| https://git.kernel.org/stable/c/3e7d0968203d668af6036b9f9199c7b62c8a3581 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/4be26d553a3f1d4f54f25353d1496c562002126d | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/6bdf4e6dfb60cbb6121ccf027d97ed2ec97c0bcb | kernel.org | |
| https://git.kernel.org/stable/c/832580af82ace363205039a8e7c4ef04552ccc1a | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/861021710bba9dfa0749a3c209a6c1773208b1f1 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/9f6ad5d533d1c71e51bdd06a5712c4fbc8768dfa | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/c79a924ed6afac1708dfd370ba66bcf6a852ced6 | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 23, 2025 | CVE Modified | kernel.org |
| Dec 9, 2025 | New CVE Received | kernel.org |