CVE-2023-53820

loop: loop_set_status_from_info() check before assignment

N/A
Published: December 9, 2025 at 01:24 AM UTC
Updated: June 17, 2026 at 06:46 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.3%

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 4.14.292v ≥ 4.9.327v ≥ 5.19.64.14.292 ≤ v < 4.154.19.257 ≤ v < 4.19.3124.9.327 ≤ v < 4.105.10.140 ≤ v < 5.10.1735.15.64 ≤ v < 5.15.1005.19.6 ≤ v < 5.205.4.212 ≤ v < 5.4.2746.0 ≤ v < 6.1.186.0 ≤ v < 6.2.56.0 ≤ v < 6.313b2856037a651ba3ab4a8b25ecab3e791926da318e28817cb516b39de6281f6db9b0618b2cc7b422035c770bfdbcc82bd52e05871a7c82db9529e0f4.14.2924.19.2574.9.327455bef69028c65065f16bb4635591b2374249b5.10.1405.15.645.19.65.4.2126.06858933131d0dadac071c4d33335a9ea4b8e76cf9be7fa7ead18a48940df7b59d993bbc8b9055c15a217715338fd48f72114725aa7a40e484a781ca7adf0112d9b8acb03485624220b4934f69bf13369b40877b8562c5720d0a7fce20729f56b75a3dedec490a0b5a4f36da3918181a8acdc6991d967c5f3
Vendor states this is fixed in 258809bf22bf71d53247856f374f2b1d055f2fd4 (fixed)
Vendor states this is fixed in 2ea7077748e5d7cc64f1c31342c802fe66ea7426 (fixed)
Vendor states this is fixed in 3e7d0968203d668af6036b9f9199c7b62c8a3581 (fixed)
Vendor states this is fixed in 4be26d553a3f1d4f54f25353d1496c562002126d (fixed)
Vendor states this is fixed in 6bdf4e6dfb60cbb6121ccf027d97ed2ec97c0bcb (fixed)
Vendor states this is fixed in 832580af82ace363205039a8e7c4ef04552ccc1a (fixed)
Vendor states this is fixed in 861021710bba9dfa0749a3c209a6c1773208b1f1 (fixed)
Vendor states this is fixed in 9f6ad5d533d1c71e51bdd06a5712c4fbc8768dfa (fixed)
Vendor states this is fixed in c79a924ed6afac1708dfd370ba66bcf6a852ced6 (fixed)
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.19.312 (unaffected)
Vendor states this is fixed in 5.10.173 (unaffected)
Vendor states this is fixed in 5.15.100 (unaffected)
Affected range stops below 5.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.4.274 (unaffected)
Vendor states this is fixed in 6.0 (unaffected)
Vendor states this is fixed in 6.1.18 (unaffected)
Vendor states this is fixed in 6.2.5 (unaffected)
Vendor states this is fixed in 6.3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card