CVE-2023-53820: loop: loop_set_status_from_info() check before assignment
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.27% (FIRST EPSS).
- Fixed version: Linux Linux 258809bf22bf71d53247856f374f2b1d055f2fd4, 2ea7077748e5d7cc64f1c31342c802fe66ea7426, 3e7d0968203d668af6036b9f9199c7b62c8a3581.
Low priority for now. Upgrade to Linux Linux 258809bf22bf71d53247856f374f2b1d055f2fd4, 2ea7077748e5d7cc64f1c31342c802fe66ea7426, 3e7d0968203d668af6036b9f9199c7b62c8a3581 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Published
- Dec 9, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 20th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 18e28817cb516b39de6281f6db9b0618b2cc7b42, adf0112d9b8acb03485624220b4934f69bf13369, 9be7fa7ead18a48940df7b59d993bbc8b9055c15, 6.0affected
- 2035c770bfdbcc82bd52e05871a7c82db9529e0f and later · before 6bdf4e6dfb60cbb6121ccf027d97ed2ec97c0bcbaffected · git
- a217715338fd48f72114725aa7a40e484a781ca7 and later · before 832580af82ace363205039a8e7c4ef04552ccc1aaffected · git
- 13b2856037a651ba3ab4a8b25ecab3e791926da3 and later · before 2ea7077748e5d7cc64f1c31342c802fe66ea7426affected · git
- b40877b8562c5720d0a7fce20729f56b75a3dede and later · before 861021710bba9dfa0749a3c209a6c1773208b1f1affected · git
- 6858933131d0dadac071c4d33335a9ea4b8e76cf and later · before c79a924ed6afac1708dfd370ba66bcf6a852ced6affected · git
- 0455bef69028c65065f16bb04635591b2374249b and later · before 3e7d0968203d668af6036b9f9199c7b62c8a3581affected · git
- c490a0b5a4f36da3918181a8acdc6991d967c5f3 and later · before 4be26d553a3f1d4f54f25353d1496c562002126daffected · git
- c490a0b5a4f36da3918181a8acdc6991d967c5f3 and later · before 258809bf22bf71d53247856f374f2b1d055f2fd4affected · git
- c490a0b5a4f36da3918181a8acdc6991d967c5f3 and later · before 9f6ad5d533d1c71e51bdd06a5712c4fbc8768dfaaffected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.20-1 | 6.1.20-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2022-50678Dec 9, 2025 · wifi: brcmfmac: fix invalid address access when enabling SCAN log level0Monitor
- ← EarlierCVE-2022-50679Dec 9, 2025 · i40e: Fix DMA mappings leak0Monitor
- Later →CVE-2023-53821Dec 9, 2025 · ip6_vti: fix slab-use-after-free in decode_session60Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 258809bf22bf71d53247856f374f2b1d055f2fd4 | Vendor (CNA) |
| Linux Linux | 2ea7077748e5d7cc64f1c31342c802fe66ea7426 | Vendor (CNA) |
| Linux Linux | 3e7d0968203d668af6036b9f9199c7b62c8a3581 | Vendor (CNA) |
| Linux Linux | 4.10 | Vendor (CNA) |
| Linux Linux | 4.15 | Vendor (CNA) |
| Linux Linux | 4.19.312 | Vendor (CNA) |
| Linux Linux | 4be26d553a3f1d4f54f25353d1496c562002126d | Vendor (CNA) |
| Linux Linux | 5.10.173 | Vendor (CNA) |
| Linux Linux | 5.15.100 | Vendor (CNA) |
| Linux Linux | 5.20 | Vendor (CNA) |
| Linux Linux | 5.4.274 | Vendor (CNA) |
| Linux Linux | 6bdf4e6dfb60cbb6121ccf027d97ed2ec97c0bcb | Vendor (CNA) |
| Linux Linux | 832580af82ace363205039a8e7c4ef04552ccc1a | Vendor (CNA) |
| Linux Linux | 861021710bba9dfa0749a3c209a6c1773208b1f1 | Vendor (CNA) |
| Linux Linux | 9f6ad5d533d1c71e51bdd06a5712c4fbc8768dfa | Vendor (CNA) |
| Linux Linux | c79a924ed6afac1708dfd370ba66bcf6a852ced6 | Vendor (CNA) |
| debian:linux | 6.1.20-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/2ea7077748e5d7cc64f1c31342c802fe66ea7426
- git.kernel.org/stable/c/3e7d0968203d668af6036b9f9199c7b62c8a3581
- git.kernel.org/stable/c/4be26d553a3f1d4f54f25353d1496c562002126d
- git.kernel.org/stable/c/6bdf4e6dfb60cbb6121ccf027d97ed2ec97c0bcb
- git.kernel.org/stable/c/832580af82ace363205039a8e7c4ef04552ccc1a
- git.kernel.org/stable/c/861021710bba9dfa0749a3c209a6c1773208b1f1
- git.kernel.org/stable/c/9f6ad5d533d1c71e51bdd06a5712c4fbc8768dfa
- git.kernel.org/stable/c/c79a924ed6afac1708dfd370ba66bcf6a852ced6
Vendor advisories and official records. Exploit/PoC links are deliberately left out.